Hi, I'm not sure about your setup, but you cannot have a slave broker in an active Tomcat instance. In case you're going to use your second Tomcat instance as a "slave" as well, then you have it since it will start when slave ActiveMQ obtain the lock. In case both Tomcat instances need to use the same broker, then you'll need a standalone ActiveMQ installation. The other option is that every Tomcat use their own broker, which can be then connected together in the network.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Thu, Feb 18, 2010 at 12:18 PM, capriipriya <priyanka.sriyapare...@ge.com>wrote: > > 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 . > > <beans > xmlns="http://www.springframework.org/schema/beans"; > xmlns:amq="http://activemq.apache.org/schema/core"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > > http://www.springframework.org/schema/beans/spring-beans-2.5.xsd > http://activemq.apache.org/schema/core > http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd > http://activemq.apache.org/camel/schema/spring > http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";> > > <amq:broker brokerName="3.204.21.219" shutdownOnMasterFailure="false"> > <amq:persistenceAdapter> > <amq:jdbcPersistenceAdapter dataSource="#oracle-ds"/> > </amq:persistenceAdapter> > > > > <amq:transportConnectors> > <amq:transportConnector uri="tcp://3.204.21.219:61616"/> > </amq:transportConnectors> > </amq:broker> > > > <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource" > destroy-method="close"> > <property name="driverClassName" > value="oracle.jdbc.driver.OracleDriver"/> > <property name="url" value="jdbc:oracle:thin:@3.204.35.53:1521:orcl"/> > <property name="username" value="system"/> > <property name="password" value="test123"/> > <property name="poolPreparedStatements" value="true"/> > </bean> > </beans> > > 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" /> > </bean>. > > 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: > http://old.nabble.com/Tomcat-does-not-start-for-slave-activeMQ-Broker-in-jdbc-master-slave-cluster-environment-tp27637368p27637368.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
