[
https://jira.jboss.org/jira/browse/JBAS-6561?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-6561:
----------------------------------
Description:
One of the TM tests in the AS fails due to what it perceives as a spec compliance failure.
However, I am not sure the test is correct.
The test starts a transaction using TransactionManager in thread 0 and then commits the
transaction in thread 1. Thread 0 then calls tm.commit(), and it expects an
IllegalStateException because the test does not think the transaction should be associated
with Thread 0 at this point.
The spec doesn't seem to say anything about Transaction.commit() causing other threads
to unassociate themselves with the Transaction. Is the test wrong?
was:
One of the TM tests in the AS fails due to what it perceives as a spec compliance failure.
However, I am not sure the test requires is correct.
The test starts a transaction using TransactionManager in thread 0 and then commits the
transaction in thread 1. Thread 0 then calls tm.commit(), and it expects an
IllegalStateException because the test does not think the transaction should be associated
with Thread 0 at this point.
The spec doesn't seem to say anything about Transaction.commit() causing other threads
to unassociate themselves with the Transaction. Is the test wrong?
Regression:
MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads() fails
---------------------------------------------------------------------------------
Key: JBAS-6561
URL:
https://jira.jboss.org/jira/browse/JBAS-6561
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transaction Manager (Arjuna)
Reporter: Jason T. Greene
Assignee: Jonathan Halliday
Fix For: JBossAS-5.1.0.Beta1
One of the TM tests in the AS fails due to what it perceives as a spec compliance
failure. However, I am not sure the test is correct.
The test starts a transaction using TransactionManager in thread 0 and then commits the
transaction in thread 1. Thread 0 then calls tm.commit(), and it expects an
IllegalStateException because the test does not think the transaction should be associated
with Thread 0 at this point.
The spec doesn't seem to say anything about Transaction.commit() causing other
threads to unassociate themselves with the Transaction. Is the test wrong?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira