activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <>
Subject [jira] [Commented] (AMQ-3696) Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi
Date Thu, 19 Jul 2012 13:00:45 GMT


Dejan Bosanac commented on AMQ-3696:

With svn revision 1363319, we now have this issue fixed.

Brokers agains start synchronously by default, which is needed for vm transport embedded case.
You can specify async start by using {{asyncStart}} property, like

{code}<broker ... startAsync="true">{code}

This config is also added to default config used in osgi.

Web console is also updated to show a specialized page for slave brokers.
> Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi
> -------------------------------------------------------------------------------
>                 Key: AMQ-3696
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: ServiceMix 4.3
>            Reporter: metatech
>         Attachments: DatabaseLockerUnblocker.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> A Blueprint container cannot be stopped while it is in the state "Creating" because both
operations are synchronized in BlueprintContainerImpl.
> The impact is that a slave broker cannot be stopped. Fortunately, before the broker itself
is stopped, first the OSGi services are unregistered, which calls the configured OSGi unregistration
> This patch provides a class which is a OSGi service unregistration listener, to allow
to stop the database locker, while it is blocked in the "Creating" state.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message