activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2551) Locking issue with MySQL InnoDB
Date Thu, 04 Nov 2010 13:23:01 GMT

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

Gary Tully resolved AMQ-2551.
-----------------------------

    Resolution: Fixed
      Assignee: Gary Tully

Added exclusive lock to the cleanup task such that it won't content with normal message addition.
Cleanup takes care of deleting messages acked by all durable subs, so very often it has nothing
to do but when it does, it needs to have exclusive access. r1030928

> Locking issue with MySQL InnoDB
> -------------------------------
>
>                 Key: AMQ-2551
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2551
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Dejan Bosanac
>            Assignee: Gary Tully
>             Fix For: 5.5.0
>
>
> Using jdbc with Mysql InnoDB, can lead to following errors
> {code}Deadlock found when trying to get lock;try restarting transaction{code}
> and messages stuck in database.
> The problem is described here http://dev.mysql.com/doc/refman/5.0/en/innodb-lock-modes.html
and is caused by unsynced cleanup task. 
> Current workaround is to turn off cleanup task like this
> {code}<jdbcPersistenceAdapter dataSource="#mysql-ds"  ... cleanupPeriod="0"/>{code}

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


Mime
View raw message