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.1 version, I've added it to issue tracking
http://issues.apache.org/activemq/browse/AMQ-1236
but it is still unassigned
--
View this message in context:
http://www.nabble.com/Failing-to-acquire-exclusive-lock---MySQL-tf3598830s2354.html#a10230629
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
