[
https://issues.apache.org/activemq/browse/AMQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53532#action_53532
]
Gabriel Kalil commented on AMQ-1473:
------------------------------------
Hi guys.
We found out that the problem occurred when the server was using a "remote
syslog" adapter (log4j). When (for some reason) the adapter fails the server
presents this behavior.
It looks like some kind of exception not correctly handled or something.
Gabriel
> 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
> Assignee: Dejan Bosanac
> Fix For: 5.4.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.
