[
https://issues.jboss.org/browse/JBTM-2135?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2135:
----------------------------------------
The failure is caused by a MySql deadlock when client0 initialises the OTSManager
(com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when
trying to get lock; try restarting transaction) whilst writing a
"FactoryContactItem" record to the store. It isn't clear from the logs which
other process and locks are involved.
The advice in the MySQL docs is:
bq. Always be prepared to re-issue a transaction if it fails due to deadlock. Deadlocks
are not dangerous. Just try again.
Do we think it is worthwhile changing retrying failed JDBCStore.write_committed
operations
QA suite failure: CrashRecovery08_Test22
----------------------------------------
Key: JBTM-2135
URL:
https://issues.jboss.org/browse/JBTM-2135
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Reporter: Gytis Trikleris
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.2
Attachments: narayana-jdbcobjectstore_67_mysql_CrashRecovery08_Test22.zip
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/6...
--
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