[jira] [Resolved] (AMQ-3696) Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-3696.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0
         Assignee: Dejan Bosanac
    
> Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-3696
>                 URL: https://issues.apache.org/jira/browse/AMQ-3696
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: ServiceMix 4.3
>            Reporter: metatech
>            Assignee: Dejan Bosanac
>             Fix For: 5.7.0
>
>         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 listeners.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira