Affects Version/s: None
Fix Version/s: None
Number of attachments :
shutdown becomes a race between components that wat to use AMQ and AMQ shutting down itself.
I posted this to amq-user before submitting this comment :
Since the BrokerService's default value for useShutdownHook is true, a shutdown hook get set up for every broker that I start.
I cannot find a simple way, to get at the broker before it is started, to setUseShutdownHook(false) - maybe I am missing something ?
This means that if someone control-c's my JVM, I have no control over when the broker actually shuts down - my code which uses AMQ during shutdown and the broker find themselves in a race....
I had a solution to this in 3.2 (I seem to remember that I could suppress the registration of the shutdown hook via a property and had found a really tortuous way to explicitly shut down the broker when I wanted to), but do not seem to be able to find one in 4.0-RC2 - is there one ?
I need a way to take on responsibility for the Broker's lifecycle and manipulate it - or that is my understanding of the situation anyway - any help would be appreciated.