activemq-users mailing list archives

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

Hi,

i'm currently trying to set up multiple master-slave-broker as described in
http://activemq.apache.org/jdbc-master-slave.html. 
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:persistenceAdapter>
        <amq:jdbcPersistenceAdapter createTablesOnStartup="false"
dataSource="#activemq-dataSource"/>
    </amq:persistenceAdapter>
    <amq:transportConnectors>
        <amq:transportConnector uri="vm://localhost" />
    </amq:transportConnectors>
</amq:broker>

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:
http://www.nabble.com/jdbcPersistence-behaviour-to13696937s2354.html#a14298283
and fixed here:
https://issues.apache.org/activemq/browse/AMQ-1519

My question is: is there any option to start the embedded broker in a
nonblocking way when its started from
org.apache.activemq.broker.XBeanBrokerService?

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

thanks in advance,
Raimund 


-- 
View this message in context: http://www.nabble.com/Non-blocking-embedded-broker-startup-when-using-jdbc-master-slave-setup-tp23988180p23988180.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message