You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2010/08/10 15:27:17 UTC
[jira] Updated: (AMQ-2414) JDBC datastore locking does not work
when using MYSQL cluster
[ https://issues.apache.org/activemq/browse/AMQ-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated AMQ-2414:
---------------------------------
Fix Version/s: 5.4.1
(was: 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.1
>
> 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.