Thanks! I'm studying up on tcpdump's man page now (about 30 pages
of technical details!). Wireshark isn't installed by default, so I
put in a request to have it installed on Tuesday. I won't be back
in until Thursday, so I'll resume my diagnostics then.
The broker and client are on the same local network, and a
traceroute takes 1.5 ms for just that one hop! That's a long
time.
Pinging is slow, too, as well as other indications of a slow
network, possibly. So I think we're barking up the right tree, but
tracking down the source of any network issues will be an arduous
task! And then we'll have to fix it if we can find it...
Mark
On 5/13/2013 3:40 PM, ceposta [via
ActiveMQ] wrote:
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.
mark_fenbers.vcf (360 bytes)
<http://activemq.2283324.n4.nabble.com/attachment/4666984/0/mark_fenbers.vcf>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Wire-Format-Negotiation-Timeout-Say-what-tp4666972p4666984.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
