[
https://issues.apache.org/activemq/browse/AMQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51688#action_51688
]
Gary Tully commented on AMQ-1473:
---------------------------------
It would be help full to see a thread dump from the server when this occurs.
A typical instance where this occurs is when the client connects to a port that
is not an activemq tcp transport endpoint. The client can connect, but it
cannot complete its handshake and times out.
An alternative is where the server is overloaded and the accept thread cannot
start due to lack of resources or is really slow to start. In this case,
extending the handshake/wireformat timeout
[option|http://activemq.apache.org/tcp-transport-reference.html| should help
but it may be best to use a network of brokers to partition the load.
In any event, a server side thread dump should help diagnose.
> javax.jms.JMSException: Wire format negociation timeout: peer did not send
> his wire format.
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-1473
> URL: https://issues.apache.org/activemq/browse/AMQ-1473
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Reporter: Denis Abramov
> Fix For: 5.3.0
>
>
> Periodically my JMS Client crashes and then can't start back up. I get the
> following exception:
> javax.jms.JMSException: Wire format negociation timeout: peer did not send
> his wire format.
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1185)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1263)
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:449)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
