activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From capriipriya <>
Subject Tomcat does not start for slave activeMQ Broker in jdbc master slave cluster environment
Date Thu, 18 Feb 2010 11:18:18 GMT

HI ,

I am using activemq within tomcat and i am deploying an application in a
clustered mode using jdbc master slave clustering.
I have two nodes -one as a master and one as a slave.
I have the same configuration in both the nodes.
The activemq.xml configuration being used is below .


<amq:broker brokerName="" shutdownOnMasterFailure="false">
            <amq:jdbcPersistenceAdapter dataSource="#oracle-ds"/>


	  <amq:transportConnector uri="tcp://"/>      

 <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"
    <property name="driverClassName"
    <property name="url" value="jdbc:oracle:thin:@"/>
    <property name="username" value="system"/>
    <property name="password" value="test123"/>
    <property name="poolPreparedStatements" value="true"/>

I have spring configuration for starting the broker as 

<bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
  		<property name="config" value="classpath:activemq.xml" /> 
  		<property name="start" value="true" /> 

The issue is that the first node's tomcat starts up properly and becomes the
master by attaining a lock on the database.When the second node's tomcat
starts ,the broker keeps trying to attain a lock on the database and the
tomcat does not start because of this.I can run this properly in a
standalone activemq deployment .But the requirement is to use an embedded
activemq in tomcat.

What can i do to overcome this issue ?

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

View raw message