[jira] Resolved: (GERONIMO-5312) support asynchronous start of ActiveMQ BrokerService

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

     [ https://issues.apache.org/jira/browse/GERONIMO-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Jiang resolved GERONIMO-5312.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.2
                   2.2.1

opened another JIRA https://issues.apache.org/jira/browse/GERONIMO-5721 to continue track this problem in 3.x.

> support asynchronous start of ActiveMQ BrokerService
> ----------------------------------------------------
>
>                 Key: GERONIMO-5312
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5312
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2.1, 3.0
>            Reporter: Kevan Miller
>            Assignee: Kevan Miller
>             Fix For: 2.2.1, 2.2.2
>
>
> 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 message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.