[
https://issues.apache.org/activemq/browse/AMQ-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2574.
--------------------------------
Resolution: Fixed
Fixed with svn revision 964847
Incidentally, destroyApplicationContextOnStop and
destroyApplicationContextOnShutdown broker attributes became obsolete and we
should use shutdown hooks instead, like
{code} <shutdownHooks>
<bean xmlns="http://www.springframework.org/schema/beans"; id="hook"
class="org.apache.activemq.hooks.SpringContextHook" />
</shutdownHooks> {code}
More stuff for blueprint support, refactorings and documentation is coming.
> 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.4.0, 5.3.1
>
>
> 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.
