[
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
