activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "raimund.fiedler" <>
Subject Non blocking embedded broker startup when using jdbc master-slave setup
Date Thu, 11 Jun 2009 20:14:06 GMT


i'm currently trying to set up multiple master-slave-broker as described in 
The current setup consists of a spring-mvc based application deployed in a
tomcat 5.5.x with an embedded activemq broker. The broker is configured with
some xbeans tags:
<amq:broker id="broker" brokerName="smava" useJmx="true" persistent="true">
        <amq:jdbcPersistenceAdapter createTablesOnStartup="false"
        <amq:transportConnector uri="vm://localhost" />

When i try to startup a second instance of the application with a second
embedded broker (wich should act as failover), the startup of the
application comes to a halt because the broker waits for a lock in the
database wich is already used by the first broker.
The same issue with deployment to jboss was discussed here:
and fixed here:

My question is: is there any option to start the embedded broker in a
nonblocking way when its started from

If not, is there a preferred way to file this issue in JIRA? 

thanks in advance,

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message