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

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

    [ https://issues.apache.org/jira/browse/AMQ-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240929#comment-14240929 ] 

metatech edited comment on AMQ-3696 at 12/10/14 10:57 AM:
----------------------------------------------------------

[~dejanb] I only had the time and opportunity to test this new feature last week in ServiceMi 4.5.3 (including ActiveMQ 5.7.0).  It works indeed fine. Thanks !


was (Author: metatech):
[~dejanb] I only had the time and opportunity to test this new feature last week in ServiceMi 4.5.0 (including ActiveMQ 5.7.0).  It works indeed fine. Thanks !

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)