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

• Key: AMQ-1273
• Type: New Feature
• Status: Open
• Priority: Major
• Assignee: Unassigned
• Reporter: James Strachan
• Component/s: Broker
• Fix Version/s: 5.4.0

Comments

[Manish Bellani]

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?

[Raphaël Ramirez]

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>