[
https://issues.apache.org/jira/browse/QPID-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-3325:
---------------------------------
Component/s: Java Broker
Fix Version/s: 0.15
Summary: make the ApplicationRegistry unregister its shutdown hook
when closed by means other than the shutdown hook (was: Make it possible to
access broker shutdown hook from outside)
Given the lack of reply to the above questions I think its past time we just
make the change we thought was most suitable and have the ApplicationRegistry
remove its shutdown hook in the event it is closed by something other than the
hook. This would allow an embeeded broker to be shut down without it leaving
behind a shutdown hook that would later run when the JVM was shut down, which I
believe is the only reasonable explanation behind the request to directly
access the thread.
Changing title from 'Make it possible to access broker shutdown hook from
outside' to 'make the ApplicationRegistry unregister its shutdown hook when
closed by means other than the shutdown hook' to reflect the actual change
being made.
> make the ApplicationRegistry unregister its shutdown hook when closed by
> means other than the shutdown hook
> -----------------------------------------------------------------------------------------------------------
>
> Key: QPID-3325
> URL: https://issues.apache.org/jira/browse/QPID-3325
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Danushka Menikkumbura
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
> Attachments: QPID-3325.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]