[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:
-----------------------------------
Comment: was deleted
(was: Sun Orb failure: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ja...)
> 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: Bug
> 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.M3
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months
[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:
-----------------------------------
Comment: was deleted
(was: Sorry, I must have forgotten to save off the build.
It happened again here:
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ja...
)
> 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: Bug
> 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.M3
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months
[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 edited comment on JBTM-1211 at 3/20/13 3:05 PM:
-----------------------------------------------------------------
Please reopen the JIRA and attach the QA test output if the problem recurs.
The problem has been occurring regularly:
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ja...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ja...
http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-narayana/...
Sun Orb failure: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ja...
Sun Orb failure: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ip...
Sun Orb failure: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ip...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-ipv6-dual...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ip...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/55/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/56/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/57/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/34/
http://172.17.131.2/job/jbossts-narayana-ipv6-dualstack/36/
http://172.17.131.2/job/btny-pulls-narayana/174/
http://172.17.131.2/job/jbossts-narayana-ipv6-dualstack/37/
JACORB:http://172.17.131.2/job/jbossts-narayana-java7/42/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/66/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/67/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/68/
http://172.17.131.2/job/jbossts-narayana-java6/69/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/72/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/109/
http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/57/
http://172.17.131.2/job/jbossts-branch417-EAP61-java6-ipv6-dualstack/191/
http://172.17.131.2/job/jbossts-branch417-EAP61-java7/543/
http://172.17.131.2/job/jbossts-branch417-EAP61-java6-ipv6-dualstack/191/
http://172.17.131.2/job/jbossts-branch417-EAP61-java7/546/
http://172.17.131.2/job/jbossts-narayana-java6/128/
http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/68
http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/70
http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/72
http://172.17.131.2/job/jbossts-EAP61/1540
http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/31
http://172.17.131.2/job/jbossts-EAP61/1734
http://172.17.131.2/job/jbossts-EAP61/1737
http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/38
was (Author: mmusgrov):
Please reopen the JIRA and attach the QA test output if the problem recurs.
> 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: Bug
> 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.M3
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months
[JBoss JIRA] (JBTM-1350) Deadlock in LockManager
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1350?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1350:
-----------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
> Deadlock in LockManager
> -----------------------
>
> Key: JBTM-1350
> URL: https://issues.jboss.org/browse/JBTM-1350
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 5.0.0.M1, 4.17.2
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 4.17.3, 5.0.0.M3
>
> Attachments: deadlock_via_intrinsic_lock, deadlock_via_ServerNestedAction, jstack.16785
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> A deadlock can occur whilst calling LockManager.setlock if another thread tries to commit a transaction that has the same lock manager as a participant. The attached java stack dump, jstack.16785, (from test com.hp.mwtests.ts.jts.remote.hammer.DistributedHammer2) shows an example. It shows two threads interacting with a remote HammerObject:
> - Thread 1 updates the remote object;
> - Thread 2 commits a transaction that has the same HammerObject instance as a participant;
> Thread 1 calls setlock on HammerObject which synchronizes on BasicAction.Current() and LockManager.locksHeldLockObject and then activates the object (which triggers an object load from the object store). The activate call tries to lock StateManager.mutex and this is where thread 1 deadlocks.
> Meanwhile a commit request is issued which results in Thread 2 running at the same time thread 1 is calling activate. The commit asks HammerObject to prepare and commit. The participant commit asks HammerObject to release any locks it has held (LockManager.releaseAll). This call first tries to lock BasicAction.Current() which is null during commit time (since commit disassociates the transaction from the thread before committing the participants). Instead it locks StateManager.mutex which succeeds. Then it tries to lock LockManager.locksHeldLockObject and that is where Thread 2 deadlocks.
> Note that the problem arises because Thread 2 gets null when it calls BasicAction.Current() and instead locks StateManager.mutex. If BasicAction.Current() was not null thread 2 would try to lock it but would not obtain the lock until thread 1 had completed the activate call and released BasicAction.Current() thus allowing thread 2 to continue as normal.
--
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
11 years, 3 months
[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:
-----------------------------------
Original Estimate: 1 day (was: 1 week)
Remaining Estimate: 1 day (was: 1 week)
> 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: Bug
> 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.M3
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 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
11 years, 3 months
[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into REST-TX component
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1364?focusedWorklogId=12428925&page=... ]
Gytis Trikleris logged work on JBTM-1364:
-----------------------------------------
Author: Gytis Trikleris
Created on: 20/Mar/13 2:38 PM
Start Date: 20/Mar/13 2:38 PM
Worklog Time Spent: 7 hours
Issue Time Tracking
-------------------
Remaining Estimate: 4 days, 1 hour (was: 1 week)
Time Spent: 7 hours
Worklog Id: (was: 12428925)
> Migrate "REST-AT to JTA" bridge into REST-TX component
> ------------------------------------------------------
>
> Key: JBTM-1364
> URL: https://issues.jboss.org/browse/JBTM-1364
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator, REST, TxBridge
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Labels: assign
> Fix For: 5.0.0.M3
>
> Original Estimate: 1 week
> Time Spent: 7 hours
> Remaining Estimate: 4 days, 1 hour
>
> The task is to the work Gytis did on his internship and migrate it into the REST-TX project.
> Tasks:
> 1. Review the current solution looking for:
> 1.1 Major issues that prevent an initial release
> 1.2 Test coverage
> 2. Make any required changes
> 3. Merge into the REST-TX project
> 4. Migrate the quickstarts accross
> 5. Create a blog post
> 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy.
--
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
11 years, 3 months
[JBoss JIRA] (JBTM-1472) Initial work on JTA for Compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1472?focusedWorklogId=12428923&page=... ]
Paul Robinson logged work on JBTM-1472:
---------------------------------------
Author: Paul Robinson
Created on: 20/Mar/13 1:15 PM
Start Date: 20/Mar/13 1:15 PM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 week, 4 days, 3 hours (was: 2 weeks)
Time Spent: 5 hours
Worklog Id: (was: 12428923)
> Initial work on JTA for Compensations
> -------------------------------------
>
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 weeks
> Time Spent: 5 hours
> Remaining Estimate: 1 week, 4 days, 3 hours
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> Tasks:
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
--
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
11 years, 3 months