I have been doing some more digging around, and noticed this: Assuming creates a org.apache.activemq.network.jms.JmsQueueConnector, which is a child class of org.apache.activemq.network.jms.SimpleJmsQueueConnector, which is a child class of org.apache.activemq.network.jms.JmsConnector, which implements org.apache.activemq.Service. Service has 2 methods listed: start() and stop(). I am also assuming when you shutdown a Embedded Broker, or a standalone instance of ActiveMQ, the stop() method is called when shutdown occurrs, correct? The stop() method on JmsQueueConnector tells each of it's DestinatinoBridges, to stop().
And All the DestinationBridge does is set started to false. I am not seeing any code that tells the Connection to close(). Is this done somewhere else? Not sure how that would happen since the Connections are on JmsQueueConnector. There is the matter of the ThreadPoolUtils.shutdown() method. Is this where the Connections are supposed to be closed? Again, I see nothing that tells the Connection to close? How do JMS Bridge Connections get closed in an Embedded Broker? Is this one of the reasons why the JMS Bridge Page says we should look at using Camel First? Should there NOT be a JMS Bridge Connection inside an Embedded Broker? -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-9-not-shutting-down-cleanly-tp4681371p4681456.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
