Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-5721

support asynchronous start of ActiveMQ BrokerService for 3.x

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.0.0
    • Fix Version/s: None
    • Component/s: ActiveMQ
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              genspring Lin Quan Jiang
              Reporter:
              genspring Lin Quan Jiang

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment