[jboss-jira] [JBoss JIRA] Created: (JBAS-3466) JMS PersistenceManager: org.jboss.mq.SpyJMSException: Could not remove message when using MySQL DB

[Luc Texier (JIRA)]

JMS PersistenceManager:  org.jboss.mq.SpyJMSException: Could not remove message when using MySQL DB
---------------------------------------------------------------------------------------------------

                 Key: JBAS-3466
                 URL: http://jira.jboss.com/jira/browse/JBAS-3466
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: JMS service
    Affects Versions: JBossAS-3.2.8.SP1, JBossAS-4.0.3 SP1
         Environment: MySQL DB with InnoDB engine 
            Reporter: Luc Texier
         Assigned To: Adrian Brock
            Priority: Minor
             Fix For: JBossAS-4.0.5.CR1



Configuring the JMS persistence manager to use MySQL DB, under load, we get 

Caused by: org.jboss.mq.SpyTransactionRolledBackException: Transaction was rolled back.; - nested throwable: (org.jboss.mq.SpyJMSException: Could not remove message: 20 msg=12 soft STORED PERSISTENT queue=QUEUE.KVSMSLogQueue priority=4 lateClone=false hashCode=19088493; - nested throwable: (java.sql.SQLException: Deadlock found when trying to get lock; try restarting transaction))
at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:490)
at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:182)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:166)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:361)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377) 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira