You can use wireshark (or tcpdump) on the broker machine to see if the client's WireFormatInfo is coming through and whether the broker is sending one. Wireshark does have a built in activemq command codec so you can see the command objects going through. You can also try things like ping or traceroute to see if the client can get to the broker.
On Mon, May 13, 2013 at 11:49 AM, fenbers <mark.fenb...@noaa.gov> wrote: > > > > > > I'm also suspecting it is a network issue, as I surmise you are by > the questions you ask. But my strength is programming, not > sysadmin. So I want to answer your questions, but don't know the > RedHat tricks or tools to determine the answers. Can you hold my > hand (figuratively) as to how I can find out if the info is getting > blocked? > > Mark > > On 5/13/2013 2:04 PM, ceposta [via > ActiveMQ] wrote: > > Mark, > > When the connection to the broker is first established, the wire > format is > > negotiated by each side sending it's preferred info. Looks like > the client > > is sending its info, but not getting anything back. Maybe take a > thread > > dump to see what's going on on the broker side... can you verify > the client > > wire info is in fact making it across the network to the broker, > or that > > the broker's info is making it back to the client? or getting > blocked > > somehow? > > > > > > On Mon, May 13, 2013 at 10:50 AM, fenbers < [hidden email] > > wrote: > > > > I'm getting the error shown in the Subject, not at first, > but after > > > ActiveMQ > > > has been working just fine for several hours. Then once > it > happens, all my > > > clients that interact with the broker reports this error. > I've found this > > > page: > > > > > > > http://activemq.apache.org/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.html > > > > > But none of the 3 issues apply in my case. Specifically, > if the host:port > > > is incorrect, how does it work fine for several hours, then > quit in the > > > middle of the night when no one is here? And I'm not > using > log4j > > > JMSAppender. And the broker is not under heavy load. > In > fact, it is idle > > > right now and I still get the error. > > > > > > It must be something else! Anyone have ideas?? > The entire > error is > > > below... > > > > > > Mark > > > > > > ERROR 2013-05-13 12:08:58,802 [main] > SendJMS.StatusProducer: Wire format > > > negotiation timeout: peer did not send his wire format. > > > javax.jms.JMSException: Wire format negotiation timeout: > peer did not send > > > his wire format. > > > at > > > > > > > > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62) > > at > > > > > > > > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1409) > > at > > > > > > > > org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1496) > > at > > > > > > > > org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:325) > > at > > > > gov.noaa.ohrfc.SendJMS.StatusProducer.run(StatusProducer.java:92) > > > at > gov.noaa.ohrfc.SendJMS.SendJMS.main(SendJMS.java:79) > > > Caused by: java.io.IOException: Wire format negotiation > timeout: peer did > > > not send his wire format. > > > at > > > > > > > > org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:98) > > at > > > > org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68) > > at > > > > > > > > org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81) > > at > > > > > > > > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:86) > > at > > > > > > > > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1380) > > ... 4 more > > > > > > > > > > > > > > > > > > -- > > > View this message in context: > > > > http://activemq.2283324.n4.nabble.com/Wire-Format-Negotiation-Timeout-Say-what-tp4666972.html > > Sent from the ActiveMQ - User mailing list archive at > Nabble.com. > > > > > > > > -- > *Christian Posta* > > http://www.christianposta.com/blog > twitter: @christianposta > > http://www.christianposta.com/blog > > > > > > If you reply to this email, your > message will be added to the discussion below: > > http://activemq.2283324.n4.nabble.com/Wire-Format-Negotiation-Timeout-Say-what-tp4666972p4666974.html > > > To unsubscribe from Wire Format Negotiation Timeout -- Say > what??, click > here . > NAML > > > > > > > mark_fenbers.vcf (360 bytes) < > http://activemq.2283324.n4.nabble.com/attachment/4666977/0/mark_fenbers.vcf > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Wire-Format-Negotiation-Timeout-Say-what-tp4666972p4666977.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
