TCP connection exhaustion

[SoumyaA]

Hi All,

We are stuck with an issue where the tcp connections made by simulator coordinator looks not getting killed and it is causing wire format and TCP Connection exhaust limit.

Below is error snapshot- 

ERROR com.itko.lisa.coordinator.TestRegistryImpl - ERROR com.itko.lisa.coordinator.TestRegistryImpl - java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://***4001***:2011/Coordinator Wire format negotiation timeout: peer did not send his wire format.; nested exception is:  com.itko.jms.JMSException: Wire format negotiation timeout: peer did not send his wire format.

ERROR com.itko.lisa.coordinator.TestRegistryImpl - ERROR com.itko.lisa.coordinator.TestRegistryImpl - java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://***4001***:2011/Simulator Wire format negotiation timeout: peer did not send his wire format.; nested exception is:  com.itko.jms.JMSException: Wire format negotiation timeout: peer did not send his wire format.

Attaching Registry and Portal Logs.

Any help will be very much appreciated

Attachment(s)

portal.log   5.51 MB 1 version

registry.log   5.15 MB 1 version

[Vaibhav Jain]

Hi Soumya,

What is the value of property "lisa.defaultRegistryConnectionTimeoutSeconds" in lisa.properties.

This property depicts the timeout value(in seconds) which is used by coordinators & simulators when connecting to a registry

The default value is 90.

Thanks.

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Sankar Natarajan]

HI Soumya

              This one would require deeper involvement. Please kindly report a support ticket.

--

regards

Sankar Natarajan