Hi James, I tried the same test with the latest 4.2 snapshot but I'm getting the same behaviour.
I wrote a short program that demonstrates the problem. It's called http://www.nabble.com/file/6298/Test.java Test.java . Notice that if the ENABLE_JMX boolean in BrokerDisconnect is set to true, the connection won't be notified that the transport connector was stopped. I'll try to dig into the ActiveMQ source code to see why JMX is preventing the listeners from being called but you could probably figure out what's going on much faster than I can. Any help would be appreciated. Emerson James.Strachan wrote: > > On 2/5/07, mers <[EMAIL PROTECTED]> wrote: >> I'm stopping a broker's TransportConnector with the connector's stop() >> method. If JMX is disabled, stopping the connector correctly fires an >> active >> connection's ExceptionListener. If JMS is enabled, the Listener doesn't >> get >> fired. >> >> Is this expected behaviour? > > No, not at all. I remember some fixes being applied in this area in > the 4.2 trunk - I wonder could you try out the current 4.2-SNAPSHOT > build & see if this problem has been fixed? > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/JMX-preventing-connector-from-stopping.-tf3174195s2354.html#a8847449 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
