You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Matías Cobiella <ma...@yahoo.com> on 2007/02/28 23:54:08 UTC
JDBC Master-Slave doesn' work with DB2
JDBC Master-Slave doesn' work with DB2
I have two brokers in a JDBC MASTER-SLAVE configuration.
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
Am I doing something wrong? Or its a SQL bug.
Thanks in Advance for your help.
Matías.
--
View this message in context: http://www.nabble.com/JDBC-Master-Slave-doesn%27-work-with-DB2-tf3323814s2354.html#a9240339
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: [Spam: 5.0] JDBC Master-Slave doesn' work with DB2
Posted by James Strachan <ja...@gmail.com>.
On 3/9/07, Matías Cobiella <ma...@yahoo.com> wrote:
>
> Hi James,
>
> I've tried with the last SNAPSHOP and the JDBC MASTER-SLAVE behavior was the
> expected. The first broker becomes MASTER and the second broker waits until
> the MASTER releases the lock.
Awesome! Many thanks for testing this!
> Thank you!
You're welcome!
--
James
-------
http://radio.weblogs.com/0112098/
Re: [Spam: 5.0] JDBC Master-Slave doesn' work with DB2
Posted by Matías Cobiella <ma...@yahoo.com>.
Hi James,
I've tried with the last SNAPSHOP and the JDBC MASTER-SLAVE behavior was the
expected. The first broker becomes MASTER and the second broker waits until
the MASTER releases the lock.
Thank you!
Matías.
James.Strachan wrote:
>
> On 3/8/07, James Strachan <ja...@gmail.com> wrote:
>> We've never tested JDBC Master-Slave with DB2. I suspect that there
>> needs to be some work on the SQL required for DB2.
>>
>> I've raised a JIRA to track this
>> http://issues.apache.org/activemq/browse/AMQ-1193
>
> I've just fixed this in trunk. I wonder do you fancy a local build to
> see if it fixes your issue?
> http://activemq.apache.org/building.html
>
> Or try tomorrow's 4.2-SNAPSHOT distro
>
> James
>
>>
>> On 2/28/07, Matías Cobiella <ma...@yahoo.com> wrote:
>> >
>> > JDBC Master-Slave doesn' work with DB2
>> >
>> >
>> > I have two brokers in a JDBC MASTER-SLAVE configuration.
>> >
>> > 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
>> >
>> >
>> > Am I doing something wrong? Or its a SQL bug.
>> >
>> > Thanks in Advance for your help.
>> >
>> > Matías.
>> > --
>> > View this message in context:
>> http://www.nabble.com/JDBC-Master-Slave-doesn%27-work-with-DB2-tf3323814s2354.html#a9240339
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >
>> >
>>
>>
>> --
>>
>> James
>> -------
>> http://radio.weblogs.com/0112098/
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/Re%3A-JDBC-Master-Slave-doesn%27-work-with-DB2-tf3367727s2354.html#a9403440
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JDBC Master-Slave doesn' work with DB2
Posted by James Strachan <ja...@gmail.com>.
On 3/8/07, James Strachan <ja...@gmail.com> wrote:
> We've never tested JDBC Master-Slave with DB2. I suspect that there
> needs to be some work on the SQL required for DB2.
>
> I've raised a JIRA to track this
> http://issues.apache.org/activemq/browse/AMQ-1193
I've just fixed this in trunk. I wonder do you fancy a local build to
see if it fixes your issue?
http://activemq.apache.org/building.html
Or try tomorrow's 4.2-SNAPSHOT distro
James
>
> On 2/28/07, Matías Cobiella <ma...@yahoo.com> wrote:
> >
> > JDBC Master-Slave doesn' work with DB2
> >
> >
> > I have two brokers in a JDBC MASTER-SLAVE configuration.
> >
> > 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
> >
> >
> > Am I doing something wrong? Or its a SQL bug.
> >
> > Thanks in Advance for your help.
> >
> > Matías.
> > --
> > View this message in context: http://www.nabble.com/JDBC-Master-Slave-doesn%27-work-with-DB2-tf3323814s2354.html#a9240339
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: JDBC Master-Slave doesn' work with DB2
Posted by James Strachan <ja...@gmail.com>.
We've never tested JDBC Master-Slave with DB2. I suspect that there
needs to be some work on the SQL required for DB2.
I've raised a JIRA to track this
http://issues.apache.org/activemq/browse/AMQ-1193
On 2/28/07, Matías Cobiella <ma...@yahoo.com> wrote:
>
> JDBC Master-Slave doesn' work with DB2
>
>
> I have two brokers in a JDBC MASTER-SLAVE configuration.
>
> 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
>
>
> Am I doing something wrong? Or its a SQL bug.
>
> Thanks in Advance for your help.
>
> Matías.
> --
> View this message in context: http://www.nabble.com/JDBC-Master-Slave-doesn%27-work-with-DB2-tf3323814s2354.html#a9240339
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/