[
https://issues.apache.org/activemq/browse/AMQ-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61226#action_61226
]
Bruce Snyder commented on AMQ-2574:
-----------------------------------
A few items of note:
# The {{XBeanBrokerService.destroyApplicationContextOnStop}} and the
{{XBeanBrokerService.destroyApplicationContextOnShutdown}} methods:
#* Are [available in
5.3.1|http://fisheye6.atlassian.com/browse/activemq/tags/activemq-5.3.1/activemq-core/src/main/java/org/apache/activemq/xbean/XBeanBrokerService.java?r=HEAD]
#* But are [deprecated in
5.4.0|http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/xbean/XBeanBrokerService.java?r=965820]
# The
[{{SpringContextHook}}|http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-spring/src/main/java/org/apache/activemq/hooks/SpringContextHook.java#r964847]
class is only available in 5.4.0
> Try to stop OSGi bundle when closing application context
> --------------------------------------------------------
>
> Key: AMQ-2574
> URL: https://issues.apache.org/activemq/browse/AMQ-2574
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.3.1, 5.4.0
>
>
> When using destroyApplicationContextOnShutdown="true", ActiveMQ will try to
> close application context when error such as database down is encountered.
> This will allow it to be cleanly stopped in an environment such as
> ServiceMix. However, when the broker is started as an OSGi bundle, the bundle
> will be left in status "started" event when the context is destroyed. We
> should try to stop the appropriate bundle in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
