On Wed, Jan 20, 2010 at 7:13 AM, Dejan Bosanac (JIRA) <[email protected]> wrote:
>
> [
> 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 901171
>
>> 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.
>
The fixes for this issue introduced required OSGi dependencies into
the XBeanBrokerService. Why would we bring OSGi into the core of the
broker in a non-optional manner? Any OSGi dependencies should be made
optional instead of required. This should have been implemented in a
separate module outside of the activemq-core by extending the
XBeanBrokerService. The OSGi Activator should also be moved out of the
activemq-core package.
Bruce
--
perl -e 'print
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
