Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <2130611551.1255427872929.JavaMail.jira@brutus>
Date: Tue, 13 Oct 2009 02:57:52 -0700 (PDT)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2414) JDBC datastore locking does not work
 when using MYSQL cluster
In-Reply-To: <1427935676.1253886651988.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Dejan Bosanac updated AMQ-2414:
-------------------------------

    Fix Version/s:     (was: 5.3.0)
                   5.4.0

> JDBC datastore locking does not work when using MYSQL cluster
> -------------------------------------------------------------
>
>                 Key: AMQ-2414
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2414
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.0
>            Reporter: Alexander Fisher
>             Fix For: 5.4.0
>
>         Attachments: mysql-cluster-locking-r818849.patch
>
>
> JDBC Master/Slave doesn't work properly for mysql cluster when the master and slave brokers are using different MYSQL frontends as would be required in a HA setup.  The code currently locks the database using a TABLE lock which are not cluster wide in mysql.
> http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-multiple-nodes.html
> The default code path uses a SELECT FOR UPDATE to get a lock.  This is supported in mysql cluster.
> The attached patch works for me.

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