AnsweredAssumed Answered

JMS Messaging Exception - ServerRequestHandler Wire Format Negotiation

Question asked by Joel NeSmith on Nov 20, 2015

Anyone have any idea as to why DevTest 8.4 might be throwing this error?  Is there a lisa property that we can set to extend the timeout time?  Seems to be ActiveMQConnection related.

 

The Coordinator log shows  the following exception:

 

Exception JMS Messaging problem with ServerRequestHandler for tcp://<THEIRSERVERNAME>: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.

  1. java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://<THEIRSERVERNAME>: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.

            at com.itko.lisa.net.Transporter.init(Transporter.java:395)

            at com.itko.lisa.net.Transporter.<init>(Transporter.java:318)

            at com.itko.lisa.net.Transporter.createTransporter(Transporter.java:277)

            at com.itko.lisa.net.Transporter.getTransporter(Transporter.java:211)

            at com.itko.lisa.net.Transporter.transport(Transporter.java:160)

            at com.itko.lisa.net.Transactor.transact(Transactor.java:68)

            at com.itko.lisa.net.ClientBase.transact(ClientBase.java:361)

            at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:271)

            at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:244)

            at com.itko.lisa.net.CoordinatorServerClient.getLabName(CoordinatorServerClient.java:76)

            at com.itko.lisa.coordinator.TestRunner.stageTest(TestRunner.java:1333)

            at com.itko.lisa.coordinator.TestRunner.stageTest(TestRunner.java:1149)

            at com.itko.lisa.testing.RegressionRunner.initialize(RegressionRunner.java:284)

            at com.itko.lisa.testing.RegressionRunner.runTest(RegressionRunner.java:245)

            at com.itko.lisa.testing.StagedSuite$1.run(StagedSuite.java:900)

            at java.lang.Thread.run(Unknown Source)

Caused by: com.itko.jms.JMSException: Wire format negotiation timeout: peer did not send his wire format.

            at com.itko.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)

            at com.itko.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1317)

            at com.itko.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1403)

            at com.itko.activemq.ActiveMQConnection.start(ActiveMQConnection.java:523)

            at com.itko.lisa.net.ActiveMQFactory.getRemoteQueueConnection(ActiveMQFactory.java:316)

            at com.itko.lisa.net.Transporter.getOrMakeConnection(Transporter.java:407)

            at com.itko.lisa.net.Transporter.init(Transporter.java:381)

            ... 15 more

Caused by: java.io.IOException: Wire format negotiation timeout: peer did not send his wire format.

            at com.itko.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:98)

            at com.itko.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)

            at com.itko.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81)

            at com.itko.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:86)

            at com.itko.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1295)

            ... 20 more

Caused by:

 

 

Installation is DevTest 8.4 running on Linux RHEL with 8GB RAM.

DevTest 8.4 in a cloud environment. 

Connected to an enterprise DBMS running in a data center not internal Derby.

DevTest Test Cases are launched to execute in parallel.

Do not know the Coordinator's -Xmx memory setting (assume default Coordinator settings).

 

Customer considering configuring  additional Coordinators but I advised against this until we know more about whether or not this is related to our internal ActiveMQ communications or load on the Coordinator.

Outcomes