On 3/9/07, Matías Cobiella <[EMAIL PROTECTED]> 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
st 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 <[EMAIL PROTECTED]>
ixed 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 <[EMAIL PROTECTED]> wrote:
>
> JDBC Master-Slave doesn' work with DB2
>
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 <[EMAIL PROTECTED]> wrote:
JDBC Master-Slave
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 BrokerSe
