activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1313) DefaultDatabaseLocker broken on MySQL 4.1
Date Mon, 20 Aug 2007 05:53:22 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Davies updated AMQ-1313:
----------------------------

    Priority: Major  (was: Critical)

> DefaultDatabaseLocker broken on MySQL 4.1
> -----------------------------------------
>
>                 Key: AMQ-1313
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1313
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 4.1.1
>            Reporter: Kenny MacLeod
>             Fix For: 5.2.0
>
>
> AMQ-992 introduced a change in 4.1.1 where the DefaultDatabaseLocker issued a LOCK TABLE
command instead of a SELECT FOR UPDATE.
> This may work with MySQL 5 ( I haven't had the chance to test that yet), but it certainly
doesn't work with MySQL 4.1.  The "LOCK TABLE" statement does not return a result set in 4.1,
so the execute() method returns false, and the locking loop never terminates.
> Given that AMQ-992 was unnecessary (see comments there for the reason why), I suggest
that the change is rolled back to using SELECT FOR UPDATE.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message