[ https://issues.jboss.org/browse/JBTM-1373?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1373: ----------------------------------- Attachment: CrashRecovery08_Test02.jbossts-branch417-EAP61-java6-jdbcobjectstore.21.tar Fails in CrashRecovery08Clients.Client01b which starts a txn, adds a CrashAbstractRecordImpl resource to the txn and then commits it. Whilst committing it gets an unexpected rolled back exception (CORBA.TRANSACTION_ROLLEDBACK). The underlying cause happens whilst writing the intentions list to a JDBC object store backed by MySQL. The actual error is: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction The deadlock is reported at line 513 JDBCImple_driver.java whilst initialising a PreparedStatement. Firstly this is the first time we have seen this error, and secondly we don't support MySQL as a object store on 4.17. I would recommend closing as will not fix and maybe investigate if it happens again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira