Take a stack trace of the broker and post it here.
On Thu, Oct 17, 2013 at 8:51 AM, JRR <j...@cisco.com> wrote: > It appears that we are using Active MQ 5.8.0 > > And we are using the Active MQ C++ client version 3.7.0. > > Is it reproducible? Well, sort of in a way. We've entered this state and > and > now it happens for every message we attempt to send (I'm assuming the QA > folks haven't reset their applications yet). > > As for restarting their tests and making it happen again? That has not been > done, yet. It in the the beginning "oh crap" phase, of investigation. My > first reaction was that it was probably an issue with the broker itself -- > which you seem to be supporting. > > However, then the next question is... is it a defect with the broker or did > we do something that caused the broker to start doing this? It usually > works > fine. > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/OpenWireFormatNegotiator-onewayWire-format-negotiation-timeout-when-creating-connection-session-tp4672902p4672951.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
