[JBoss JIRA] (JBTM-1373) org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery08 test failed on jbossts-branch417-EAP61-java6-jdbcobjectstore
by Michael Musgrove (JIRA)
[ 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.
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery08 test failed on jbossts-branch417-EAP61-java6-jdbcobjectstore
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1373
> URL: https://issues.jboss.org/browse/JBTM-1373
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Fix For: 4.17.4
>
> Attachments: CrashRecovery08_Test02.jbossts-branch417-EAP61-java6-jdbcobjectstore.21.tar
>
>
> See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6-jdbcobjectstore/20/
> Failed tests:
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery08
--
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
12 years, 1 month
[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1211:
-----------------------------------
Attachment: jbossts-narayana-java6-ipv6-dualstack.57.tar
Both http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/57/ and http://172.17.131.2/job/jbossts-branch417-EAP61-java7/543/ fail in JTSRemote_TimeoutTest.
The scenario is TimeoutClient invokes remote object setget_i (using explicit txn propagation). The remote object uses ExplicitInterposition to register the propagated transaction which fails because the propagated transaction has timed out.
http://172.17.131.2/job/jbossts-branch417-EAP61-java6-ipv6-dualstack/191/
This one failed in JTSRemote_DistributedHammerTest2. The client starts a txn updates a remote object but the update fails because the transaction times out (marked rollback only by the reaper) before the remote object returns its response.
> Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
> ------------------------------------------------------------------------------
>
> Key: JBTM-1211
> URL: https://issues.jboss.org/browse/JBTM-1211
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS, Testing, Transaction Core
> Affects Versions: 4.16.4
> Reporter: Paul Robinson
> Assignee: Michael Musgrove
> Fix For: 4.17.4, 5.0.0.M2
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
>
> See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232
> {code}
> Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
> [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec
> {code}
--
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
12 years, 1 month