You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "metatech (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 15:19:53 UTC
[jira] [Created] (AMQ-3696) Slave broker cannot be stopped in a
JDBC Master/Slave configuration within OSGi
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
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
[jira] [Commented] (AMQ-3696) Slave broker cannot be stopped in a
JDBC Master/Slave configuration within OSGi
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQ-3696) Slave broker cannot be stopped in a
JDBC Master/Slave configuration within OSGi
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418261#comment-13418261 ]
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: 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
[jira] [Updated] (AMQ-3696) Slave broker cannot be stopped in a
JDBC Master/Slave configuration within OSGi
Posted by "metatech (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
metatech updated AMQ-3696:
--------------------------
Attachment: DatabaseLockerUnblocker.patch
> 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
[jira] [Resolved] (AMQ-3696) Slave broker cannot be stopped in a
JDBC Master/Slave configuration within OSGi
Posted by "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