Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <6767377.1189546342589.JavaMail.jira@brutus>
Date: Tue, 11 Sep 2007 14:32:22 -0700 (PDT)
From: "Dan Rudman (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1313) DefaultDatabaseLocker broken on MySQL
 4.1
In-Reply-To: <20154340.1183634133765.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Dan Rudman commented on AMQ-1313:
---------------------------------

This is a major, major issue and I am very concerned that it appears to be up for fix on the 5.2.0 release.  As my company will not deploy the 5.x release of ActiveMQ for quite some time as it is nowhere near stable (or performant, it seems) as 4.1.x, I would like to recommend that a follow-up release to 4.1.1 (4.1.2?) be made as soon as possible.

Or, at the very least, provide us with a patch to fix this issue.

Thanks for your consideration.

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