You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2010/12/01 07:16:10 UTC
[jira] Created: (GERONIMO-5721) support asynchronous start of
ActiveMQ BrokerService for 3.x
support asynchronous start of ActiveMQ BrokerService for 3.x
------------------------------------------------------------
Key: GERONIMO-5721
URL: https://issues.apache.org/jira/browse/GERONIMO-5721
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 3.0-M2, 3.0
Reporter: Shawn Jiang
It's possible to configure master-slave configurations of ActiveMQ running within a Geronimo server. However, when a BrokerService is going to be a "slave" instance, brokerService.start() will block indefinitely. In order to support master-slave configurations, I'd like to allow a BrokerService to start asynchronously (not holding up Geronimo server startup).
Note that client configuration (connector/mdb) is a bit tricky... You need to configure clients to use the ActiveMQ discovery or failover protocols. Clients need to be able to find and connect to the master broker. VM or simple tcp-ip configuration won't work.
This is opened to continue track this problem[1] in Geronimo 3.x.
[1]https://issues.apache.org/jira/browse/GERONIMO-5312
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Commented] (GERONIMO-5721) support asynchronous start of
ActiveMQ BrokerService for 3.x
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021982#comment-13021982 ]
Shawn Jiang commented on GERONIMO-5721:
---------------------------------------
The fix to this issue was applied to BrokerServiceGBeanImpl.java which was removed after 3.0 starts to use blueprint to start the broker.
Can any one confirm if we still need to track this issue ?
> support asynchronous start of ActiveMQ BrokerService for 3.x
> ------------------------------------------------------------
>
> Key: GERONIMO-5721
> URL: https://issues.apache.org/jira/browse/GERONIMO-5721
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 3.0-M2, 3.0
> Reporter: Shawn Jiang
>
> It's possible to configure master-slave configurations of ActiveMQ running within a Geronimo server. However, when a BrokerService is going to be a "slave" instance, brokerService.start() will block indefinitely. In order to support master-slave configurations, I'd like to allow a BrokerService to start asynchronously (not holding up Geronimo server startup).
> Note that client configuration (connector/mdb) is a bit tricky... You need to configure clients to use the ActiveMQ discovery or failover protocols. Clients need to be able to find and connect to the master broker. VM or simple tcp-ip configuration won't work.
> This is opened to continue track this problem[1] in Geronimo 3.x.
> [1]https://issues.apache.org/jira/browse/GERONIMO-5312
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-5721) support asynchronous start of
ActiveMQ BrokerService for 3.x
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang reassigned GERONIMO-5721:
-------------------------------------
Assignee: Shawn Jiang
> support asynchronous start of ActiveMQ BrokerService for 3.x
> ------------------------------------------------------------
>
> Key: GERONIMO-5721
> URL: https://issues.apache.org/jira/browse/GERONIMO-5721
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 3.0-M2, 3.0
> Reporter: Shawn Jiang
> Assignee: Shawn Jiang
>
> It's possible to configure master-slave configurations of ActiveMQ running within a Geronimo server. However, when a BrokerService is going to be a "slave" instance, brokerService.start() will block indefinitely. In order to support master-slave configurations, I'd like to allow a BrokerService to start asynchronously (not holding up Geronimo server startup).
> Note that client configuration (connector/mdb) is a bit tricky... You need to configure clients to use the ActiveMQ discovery or failover protocols. Clients need to be able to find and connect to the master broker. VM or simple tcp-ip configuration won't work.
> This is opened to continue track this problem[1] in Geronimo 3.x.
> [1]https://issues.apache.org/jira/browse/GERONIMO-5312
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5721) support asynchronous start of
ActiveMQ BrokerService for 3.x
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang closed GERONIMO-5721.
---------------------------------
Resolution: Won't Fix
We don't have fine control to the broker service lifecycle after we move to blueprint in 3.0
> support asynchronous start of ActiveMQ BrokerService for 3.x
> ------------------------------------------------------------
>
> Key: GERONIMO-5721
> URL: https://issues.apache.org/jira/browse/GERONIMO-5721
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 3.0
> Reporter: Shawn Jiang
> Assignee: Shawn Jiang
>
> It's possible to configure master-slave configurations of ActiveMQ running within a Geronimo server. However, when a BrokerService is going to be a "slave" instance, brokerService.start() will block indefinitely. In order to support master-slave configurations, I'd like to allow a BrokerService to start asynchronously (not holding up Geronimo server startup).
> Note that client configuration (connector/mdb) is a bit tricky... You need to configure clients to use the ActiveMQ discovery or failover protocols. Clients need to be able to find and connect to the master broker. VM or simple tcp-ip configuration won't work.
> This is opened to continue track this problem[1] in Geronimo 3.x.
> [1]https://issues.apache.org/jira/browse/GERONIMO-5312
--
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