[seam-issues] [JBoss JIRA] (SEAMTRANSACTION-9) testsuite failures with "thread is already associated with a transaction" on AS6

[Jason Porter (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/SEAMTRANSACTION-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Porter resolved SEAMTRANSACTION-9.
----------------------------------------

    Resolution: Rejected


For AS related bugs we're going to focus on AS7
                
> testsuite failures with "thread is already associated with a transaction" on AS6
> --------------------------------------------------------------------------------
>
>                 Key: SEAMTRANSACTION-9
>                 URL: https://issues.jboss.org/browse/SEAMTRANSACTION-9
>             Project: Seam Transaction
>          Issue Type: Bug
>    Affects Versions: 3.1.0.CR1
>         Environment: JBoss AS 6.0.0.Final, 6.1.0.Final
>            Reporter: Marek Schmidt
>            Assignee: Jason Porter
>             Fix For: 3.1.0.Final
>
>
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.jboss.seam.transaction.test.jboss.TransactionInterceptorStereotypeTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 9.078 sec <<< FAILURE!
> Running org.jboss.seam.transaction.test.jboss.TransactionAttributeInterceptorTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.059 sec <<< FAILURE!
> Running org.jboss.seam.transaction.test.jboss.NonEEThreadTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.243 sec
> Running org.jboss.seam.transaction.test.jboss.UserTransactionTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.898 sec <<< FAILURE!
> Running org.jboss.seam.transaction.test.jboss.TransactionInterceptorTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.846 sec <<< FAILURE!
> Running org.jboss.seam.transaction.test.jboss.TransactionScopedTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.942 sec <<< FAILURE!
> Results :
> Tests in error: 
>   testTransactionInterceptor(org.jboss.seam.transaction.test.jboss.TransactionInterceptorStereotypeTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
>   testTransactionInterceptorMethodOverrides(org.jboss.seam.transaction.test.jboss.TransactionInterceptorStereotypeTest): Unexpected exception, expected<javax.persistence.TransactionRequiredException> but was<java.lang.Exception>
>   testTransactionInterceptor(org.jboss.seam.transaction.test.jboss.TransactionAttributeInterceptorTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
>   testTransactionInterceptorMethodOverrides(org.jboss.seam.transaction.test.jboss.TransactionAttributeInterceptorTest): Unexpected exception, expected<javax.persistence.TransactionRequiredException> but was<java.lang.Exception>
>   userTransactionTest(org.jboss.seam.transaction.test.jboss.UserTransactionTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
>   synchronizationsTest(org.jboss.seam.transaction.test.jboss.UserTransactionTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
>   testTransactionInterceptor(org.jboss.seam.transaction.test.jboss.TransactionInterceptorTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
>   testTransactionInterceptorMethodOverrides(org.jboss.seam.transaction.test.jboss.TransactionInterceptorTest): Unexpected exception, expected<javax.persistence.TransactionRequiredException> but was<java.lang.Exception>
>   transactionScopeTest(org.jboss.seam.transaction.test.jboss.TransactionScopedTest): BaseTransaction.checkTransactionState - ARJUNA-16051 thread is already associated with a transaction!
> Tests run: 10, Failures: 0, Errors: 9, Skipped: 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira