By the way, as a side note, its pretty weird this bug hadn't been discovered
before because UDP actually did not work at all. So, I think there is a
serious lack of UDP tests in the current test collection.
-Amir
--
View this message in context:
http://activemq.2283324.n4.nabble.co
Thanks Gary,
Using the the pointer you gave me I found the bug in ActiveMQ that was
causing this problem. I'll submit a patch soon.
-Amir
--
View this message in context:
http://activemq.2283324.n4.nabble.com/UDP-Transport-connector-listens-on-a-random-port-number-tp3570237p35
the bug but it still exists, since 5.4 or maybe even before.
-Amir
--
View this message in context:
http://activemq.2283324.n4.nabble.com/UDP-Transport-connector-listens-on-a-random-port-number-tp3570237p3570726.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
roker is restarted.
Interestingly, the management console indicates that the broker's listening
on the configured port number but netstat shows another UDP port number. Any
idea ?
-Amir
--
View this message in context:
http://activemq.2283324.n4.nabble.com/UDP-Transport-connector-binds-t
