Unfortunately this is looking suspiciously like an inter-version
interop problem - its looking like the Client's ConnectionInfo does
not appear to have a ConnectionId when the broker reads it.
Unfortunately it looks from this log like 4.0.1 and 4.1 do not
interoperate :(
On 2/12/07, Thomas Swind
Appologies if this has already been recorded in a defect somewhere.
I am running an ActiveMQ 4.1 broker. Another team have developed a client
based upon ActiveMQ 4.0.1. They are running it within Tomcat and were having
probems with their service starting as it was failing to connect to my
broker.
