ActiveMQ
  1. ActiveMQ
  2. AMQ-1273

allow JDBC master/slave to startup asynchronously so that applications using a slave don't block on startup

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: NEEDS_REVIEW
    • Component/s: Broker
    • Labels:
      None

      Activity

      Hide
      Raphaël Ramirez added a comment -

      This request looks fixed for a J2EE compliant server, (https://issues.apache.org/activemq/browse/AMQ-1519) but it didn't fix the problem for an embedded broker in Tomcat for example.

      But thank to Samuel Liard, the solution for non a J2EE servers is now given here : http://www.net-liard.com/blog/2009/04/activemq/

      The ThreadBrokerFactoryBean.java file is found in his application sample :
      http://www.net-liard.com/blog/wp-content/uploads/2009/04/activemq.zip

      However, I've attached a modified version that may be directly called from a Spring configuration file.
      You just have to add start="false" in your existing broker declaration and reference your broker in the brokerFactory bean declaration.

      <amq:broker id="myBrokerService" start="false">
      ...
      </amq:broker>

      <bean id="brokerFactory" class="app.activemq.ThreadBrokerFactory">
      <property name="brokerService" ref="myBrokerService"/>
      </bean>

      Show
      Raphaël Ramirez added a comment - This request looks fixed for a J2EE compliant server, ( https://issues.apache.org/activemq/browse/AMQ-1519 ) but it didn't fix the problem for an embedded broker in Tomcat for example. But thank to Samuel Liard, the solution for non a J2EE servers is now given here : http://www.net-liard.com/blog/2009/04/activemq/ The ThreadBrokerFactoryBean.java file is found in his application sample : http://www.net-liard.com/blog/wp-content/uploads/2009/04/activemq.zip However, I've attached a modified version that may be directly called from a Spring configuration file. You just have to add start="false" in your existing broker declaration and reference your broker in the brokerFactory bean declaration. <amq:broker id="myBrokerService" start="false"> ... </amq:broker> <bean id="brokerFactory" class="app.activemq.ThreadBrokerFactory"> <property name="brokerService" ref="myBrokerService"/> </bean>
      Hide
      Manish Bellani added a comment -

      We have exact same problem in our application at the moment, i'm trying an approach where i am starting the broker in the separate thread. any other tips i can use? is there a patch available for this feature?

      Show
      Manish Bellani added a comment - We have exact same problem in our application at the moment, i'm trying an approach where i am starting the broker in the separate thread. any other tips i can use? is there a patch available for this feature?

        People

        • Assignee:
          Unassigned
          Reporter:
          james strachan
        • Votes:
          1 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:

            Development