activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: JDBC Master-Slave problem with DB2
Date Tue, 06 Mar 2007 09:42:14 GMT
This looks like a DB2 issue; the SQL we execute to get an exclusive
lock on the database does not appear to work propertly - we'll
probably have to tweak it for DB2. Fancy helping to figure out the
correct DB2 syntax to get an exclusive lock?


On 3/5/07, Matías Cobiella <matiascobiella@yahoo.com> wrote:
>
> Hi,
>
> I have two brokers in a JDBC MASTER-SLAVE configuration with a DB2 database
> and I'm having the
> following problem:
>
> When BrokerA starts it becomes the MASTER:
>
> INFO  BrokerService                  - Using Persistence Adapter:
> JDBCPersistenceAdaptor(org.apache.commons.dbcp.BasicDataSource
> INFO  BrokerService                  - ActiveMQ null JMS Message Broker
> (MASTER) 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:1299/jmxrmi
> INFO  JDBCPersistenceAdapter         - Database driver recognized:
> [ibm_db2_jdbc_universal_driver_architecture]
> 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@60991f
> INFO  TransportServerThreadSupport   - Listening for connections at:
> tcp://MT13412:11111
>
> But when BrokerB starts it becomes the MASTER too:
>
> INFO  BrokerService                  - Using Persistence Adapter:
> JDBCPersistenceAdaptor(org.apache.commons.dbcp.BasicDataSource
> INFO  BrokerService                  - ActiveMQ null JMS Message Broker
> (SLAVE) 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:12980/jmxrmi
> INFO  JDBCPersistenceAdapter         - Database driver recognized:
> [ibm_db2_jdbc_universal_driver_architecture]
> 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@f47396
> INFO  TransportServerThreadSupport   - Listening for connections at:
> tcp://MT13412:22222
>
>
> Both Brokers uses this db config:
>
>   <bean id="db2datasource" class="org.apache.commons.dbcp.BasicDataSource">
>     <property name="driverClassName" value="com.ibm.db2.jcc.DB2Driver"/>
>     <property name="url" value="jdbc:db2://10.250.0.73:60152/DBCCCD"/>
>     <property name="username" value="dbcccd"/>
>     <property name="password" value="cccd00"/>
>   </bean>
>
>
>
> I think this problem looks like a MySQL issue but for DB2:
>
> http://issues.apache.org/activemq/browse/AMQ-992
>
> I'm using the 4.2 SNAPSHOT
>
> Am I doing something wrong? Or its a SQL bug for DB2.
>
>
> Thanks in Advance for your help.
>
> Matías.
> --
> View this message in context: http://www.nabble.com/JDBC-Master-Slave-problem-with-DB2-tf3352149s2354.html#a9321910
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message