activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SuoNayi (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-2414) JDBC datastore locking does not work when using MYSQL cluster
Date Fri, 30 Dec 2011 01:37:30 GMT


SuoNayi commented on AMQ-2414:

Other tow problems when testing with ndbcluster.
1)No distributed table locks support yet, so it's impossible to set up a master/slave broker
for HA with ndbcluster.
2)Low performance and from time to time producer is suspended and resumes to send messages
for several minutes.
> JDBC datastore locking does not work when using MYSQL cluster
> -------------------------------------------------------------
>                 Key: AMQ-2414
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.0
>            Reporter: Alexander Fisher
>             Fix For: 5.6.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.
> The default code path uses a SELECT FOR UPDATE to get a lock.  This is supported in mysql
> The attached patch works for me.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message