activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From naga007 <NSo...@gmail.com>
Subject Re: [Spam: 5.0] Master Slave locking with MYSQL is not working with 4.1.1
Date Wed, 14 Mar 2007 14:41:51 GMT

Here is the log on master
Loading message broker from: xbean:activemq.xml
INFO  BrokerService                  - ActiveMQ 4.1.1 JMS Message Broker
(localhost) is starting
INFO  BrokerService                  - For help or more information please
see: http://incubator.apache.org/activemq/
INFO  ManagementContext              - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:7099/jmxrmi
INFO  JDBCPersistenceAdapter         - Database driver recognized:
[mysql-ab_jdbc_driver]
INFO  DefaultDatabaseLocker          - Attempting to acquire the exclusive
lock to become the Master broker
INFO  DefaultDatabaseLocker          - Becoming the master on dataSource:
org.apache.commons.dbcp.BasicDataSource@d5c0f9
INFO  TransportServerThreadSupport   - Listening for connections at:
tcp://meltsjssapp01.americanhm.com:61616
INFO  TransportConnector             - Connector openwire Started
INFO  NetworkConnector               - Establishing network connection
between from vm://localhost?network=true to
failover:(tcp://10.10.209.74:61616)?maxReconnectDelay=1000
INFO  TransportConnector             - Connector vm://localhost Started
INFO  NetworkConnector               - Network Connector MasterToSlave
Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker
(localhost, ID:meltsjssapp01.americanhm.com-57783-1173838768443-1:0) started
INFO  DemandForwardingBridge         - Network connection between
vm://localhost#0 and tcp://10.10.209.74:61616(localhost) has been
established.
INFO  FailoverTransport    

Here is the slave broker log

Loading message broker from: xbean:activemq.xml
INFO  BrokerService                  - ActiveMQ 4.1.1 JMS Message Broker
(localhost) is starting
INFO  BrokerService                  - For help or more information please
see: http://incubator.apache.org/activemq/
INFO  ManagementContext              - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO  JDBCPersistenceAdapter         - Database driver recognized:
[mysql-ab_jdbc_driver]
INFO  DefaultDatabaseLocker          - Attempting to acquire the exclusive
lock to become the Master broker
INFO  DefaultDatabaseLocker          - Becoming the master on dataSource:
org.apache.commons.dbcp.BasicDataSource@8c5ea2
INFO  TransportServerThreadSupport   - Listening for connections at:
tcp://10.10.209.74:61616
INFO  TransportConnector             - Connector openwire Started
INFO  NetworkConnector               - Establishing network connection
between from vm://localhost?network=true to
failover:(tcp://10.10.209.73:61616)?maxReconnectDelay
=1000
INFO  TransportConnector             - Connector vm://localhost Started
INFO  NetworkConnector               - Network Connector SlaveToMaster
Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker
(localhost, ID:meltsjssapp02.americanhm.com-39766-1173839316152-1:0) started
INFO  DemandForwardingBridge         - Network connection between
vm://localhost#0 and tcp://10.10.209.73:61616(localhost) has been
established.




James.Strachan wrote:
> 
> On 3/14/07, naga007 <NSogal@gmail.com> wrote:
>>
>> Thare are no errors, but both become the master.
> 
> Could you post the log please? I wonder which jdbc driver is being
> used (we try to auto-detect the driver and use the correct JDBC
> adapter based on the driver name)
> -- 
> 
> James
> -------
> http://radio.weblogs.com/0112098/
> 
> 

-- 
View this message in context: http://www.nabble.com/Master-Slave-locking-with-MYSQL-is-not-working-with-4.1.1-tf3399897s2354.html#a9475786
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message