You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2009/11/20 20:15:52 UTC

[jira] Updated: (AMQ-1313) DefaultDatabaseLocker broken on MySQL 4.1

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

Bruce Snyder updated AMQ-1313:
------------------------------

    Fix Version/s:     (was: AGING_TO_DIE)
                   4.1.3

> 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: 4.1.3
>
>
> 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.