activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From osian <>
Subject Clustering Brokers
Date Tue, 16 May 2006 11:13:00 GMT

Hi All,

I have the following file configured for my broker, and now I want to start
up multiples using this setup (which I believe is ok for clustering), but
unfortunately, this setup seems to cause the brokers and the consumers to
hang after a certain amount of processing.  note that the consumers are
using the following to connect

activemq.xml - 

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="">

    <broker brokerName="O-HUGHES" useJmx="true" useShutdownHook="true"
persistent="true" deleteAllMessagesOnStartup="false">

			<transportConnector uri="tcp://localhost:61616"
			<networkConnector uri="multicast://ProactJMSService">
				name = proact_queue
				dynamicOnly = true
					<topic physicalName=">"/>

			<jdbcPersistenceAdapter cleanupPeriod="600000" dataSource="#oracle-ds"

==================================================================== -->
    <!-- JDBC DataSource Configurations -->
==================================================================== -->

    <!-- The Datasource that will be used by the Broker -->
	<bean id="oracle-ds" class="net.proact.scm.sql.ProactPoolingDataSource">
		<property name="url" value="jdbc:oracle:oci:@CNHDEV"/>
		<property name="userName" value="CNHDEV"/>
		<property name="password" value="CNHDEV"/>

	<bean id="broker-statements"
		<property name="tablePrefix" value="BROKER_1"/>

Any ideas what is wrong with this config?


p.s. Each broker setup has a different table prefix so that it talks to its
own set of tables
View this message in context:
Sent from the ActiveMQ - User forum at

View raw message