Re: Failing to acquire exclusive lock - MySQL

2007-04-30 Thread James Strachan
On 4/30/07, Anthrope <[EMAIL PROTECTED]> wrote: Sure. Apologies for not providing that up-front; I had just hacked up a solution in order to get on. Anyway, I found that there was an issue was on line 59 in DefaultDatabaseLocker.java: boolean answer = statement.execute(); if (a

Re: Failing to acquire exclusive lock - MySQL

2007-04-30 Thread Anthrope
Sure. Apologies for not providing that up-front; I had just hacked up a solution in order to get on. Anyway, I found that there was an issue was on line 59 in DefaultDatabaseLocker.java: boolean answer = statement.execute(); if (answer) { break;

Re: Failing to acquire exclusive lock - MySQL

2007-04-30 Thread James Strachan
On 4/26/07, Anthrope <[EMAIL PROTECTED]> wrote: There is a bug in the 4.1.1 release version of DefaultDatabaseLocker.java. The problem is that the result of the execution of the prepared statement to lock the database row is being incorrectly interpreted. This link ought to explain why: http://

Re: Failing to acquire exclusive lock - MySQL

2007-04-28 Thread Mykola
Anthrope wrote: > > There is a bug in the 4.1.1 release version of DefaultDatabaseLocker.java. > The problem is that the result of the execution of the prepared statement > to lock the database row is being incorrectly interpreted. This link ought > to explain why: > > This bug exist also in 4

Re: Failing to acquire exclusive lock - MySQL

2007-04-25 Thread Anthrope
There is a bug in the 4.1.1 release version of DefaultDatabaseLocker.java. The problem is that the result of the execution of the prepared statement to lock the database row is being incorrectly interpreted. This link ought to explain why: http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Prepared

Re: Failing to acquire exclusive lock - MySQL

2007-04-25 Thread James Strachan
On 4/18/07, millea1 <[EMAIL PROTECTED]> wrote: James.Strachan wrote: > > Which version of MySQL are you using? You are not running multiple > brokers against the same database are you by any chance? > > I have this same problem when upgrading from 4.1 to 4.1.1 (mysql version > 5.0.19) in a JBo

Re: Failing to acquire exclusive lock - MySQL

2007-04-25 Thread Mykola
Hi all, Similar problem :( I'm new to ActiveMQ so probably I misconfigure it somehow. Problem: I'm trying to setup jdbcPersistenceAdapter in AMQ 4.1.1 to store journal into the MySQL 5.0.24 with Connector mysql-connector-java-5.0.4 under Windows XP My config file is very simple ---

Re: Failing to acquire exclusive lock - MySQL

2007-04-18 Thread mjanveaux
Hi, I'm using MySQL 5.0.37 and it is the only broker configured. If I switch to using derby, the exact same configuration works flawlessly... James.Strachan wrote: > > Which version of MySQL are you using? You are not running multiple > brokers against the same database are you by any chance

Re: Failing to acquire exclusive lock - MySQL

2007-04-18 Thread millea1
James.Strachan wrote: > > Which version of MySQL are you using? You are not running multiple > brokers against the same database are you by any chance? > > I have this same problem when upgrading from 4.1 to 4.1.1 (mysql version > 5.0.19) in a JBoss integration; the only broker running against

Re: Failing to acquire exclusive lock - MySQL

2007-04-17 Thread James Strachan
Which version of MySQL are you using? You are not running multiple brokers against the same database are you by any chance? On 4/18/07, mjanveaux <[EMAIL PROTECTED]> wrote: Hello, I recently upgraded to ActiveMQ 4.1.1 from 4.0.1 I integrated ActiveMQ into my application using spring but not

Re: Failing to acquire exclusive lock - MySQL

2007-04-17 Thread mjanveaux
Just additional information - this only happens when using mySQL - I tried this using derby and it works fine... I"m using mysql 5.0.37 mjanveaux wrote: > > Hello, > > I recently upgraded to ActiveMQ 4.1.1 from 4.0.1 I integrated ActiveMQ > into my application using spring but not using the s