Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 18 Jul 2012 14:14:34 +0000 (UTC)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <73577026.69069.1342620874434.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1121525431.7390.1328278793436.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3696) Slave broker cannot be stopped in a
 JDBC Master/Slave configuration within OSGi
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dejan Bosanac commented on AMQ-3696:
------------------------------------

svn revision 1362950 changes the behavior of start() method, in that it will not block for slave scenario. This change should fix the root of this problem.

One side-effect is that in standalone scenario, web console is started for slaves as well. I need to fix web console to show meaningful display for slaves as well.
                
> 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
>         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