[JBoss JIRA] (JBTM-2029) TransactionScopedTest failed
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2029?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2029:
----------------------------------------
The set holding the debugging timestamps must be corrupt. I will synchronize updates to it.
> TransactionScopedTest failed
> ----------------------------
>
> Key: JBTM-2029
> URL: https://issues.jboss.org/browse/JBTM-2029
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 5.0.0.CR2
>
> Attachments: com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest-output.txt
>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.881 sec <<< FAILURE!
> testTxAssociationChangeConcurrently(com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest) Time elapsed: 0.394 sec <<< ERROR!
> java.lang.Exception: Concurrent testTxAssociationChange failed with exception
> at java.util.TreeMap.rotateLeft(TreeMap.java:2060)
> at java.util.TreeMap.fixAfterInsertion(TreeMap.java:2127)
> at java.util.TreeMap.put(TreeMap.java:574)
> at java.util.TreeSet.add(TreeSet.java:255)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.addTimestamp(TransactionScopedTest.java:88)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.testTxAssociationChange(TransactionScopedTest.java:104)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.access$000(TransactionScopedTest.java:54)
> Running com.hp.mwtests.ts.jta.cdi.transactional.TransactionalImplTest
> Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.783 sec
> Results :
> Tests in error:
> TransactionScopedTest.testTxAssociationChangeConcurrently:179 Concurrent test...
> Tests run: 28, Failures: 0, Errors: 1, Skipped: 0
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2029) TransactionScopedTest failed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2029?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2029:
--------------------------------
Attachment: com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest-output.txt
This is the log file, it shows an NPE
> TransactionScopedTest failed
> ----------------------------
>
> Key: JBTM-2029
> URL: https://issues.jboss.org/browse/JBTM-2029
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.CR2
>
> Attachments: com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest-output.txt
>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.881 sec <<< FAILURE!
> testTxAssociationChangeConcurrently(com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest) Time elapsed: 0.394 sec <<< ERROR!
> java.lang.Exception: Concurrent testTxAssociationChange failed with exception
> at java.util.TreeMap.rotateLeft(TreeMap.java:2060)
> at java.util.TreeMap.fixAfterInsertion(TreeMap.java:2127)
> at java.util.TreeMap.put(TreeMap.java:574)
> at java.util.TreeSet.add(TreeSet.java:255)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.addTimestamp(TransactionScopedTest.java:88)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.testTxAssociationChange(TransactionScopedTest.java:104)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.access$000(TransactionScopedTest.java:54)
> Running com.hp.mwtests.ts.jta.cdi.transactional.TransactionalImplTest
> Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.783 sec
> Results :
> Tests in error:
> TransactionScopedTest.testTxAssociationChangeConcurrently:179 Concurrent test...
> Tests run: 28, Failures: 0, Errors: 1, Skipped: 0
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2029) TransactionScopedTest failed
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2029?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2029:
--------------------------------
Assignee: Michael Musgrove (was: Tom Jenkinson)
> TransactionScopedTest failed
> ----------------------------
>
> Key: JBTM-2029
> URL: https://issues.jboss.org/browse/JBTM-2029
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 5.0.0.CR2
>
> Attachments: com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest-output.txt
>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.881 sec <<< FAILURE!
> testTxAssociationChangeConcurrently(com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest) Time elapsed: 0.394 sec <<< ERROR!
> java.lang.Exception: Concurrent testTxAssociationChange failed with exception
> at java.util.TreeMap.rotateLeft(TreeMap.java:2060)
> at java.util.TreeMap.fixAfterInsertion(TreeMap.java:2127)
> at java.util.TreeMap.put(TreeMap.java:574)
> at java.util.TreeSet.add(TreeSet.java:255)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.addTimestamp(TransactionScopedTest.java:88)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.testTxAssociationChange(TransactionScopedTest.java:104)
> at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.access$000(TransactionScopedTest.java:54)
> Running com.hp.mwtests.ts.jta.cdi.transactional.TransactionalImplTest
> Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.783 sec
> Results :
> Tests in error:
> TransactionScopedTest.testTxAssociationChangeConcurrently:179 Concurrent test...
> Tests run: 28, Failures: 0, Errors: 1, Skipped: 0
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2029) TransactionScopedTest failed
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2029:
-----------------------------------
Summary: TransactionScopedTest failed
Key: JBTM-2029
URL: https://issues.jboss.org/browse/JBTM-2029
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.CR2
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.881 sec <<< FAILURE!
testTxAssociationChangeConcurrently(com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest) Time elapsed: 0.394 sec <<< ERROR!
java.lang.Exception: Concurrent testTxAssociationChange failed with exception
at java.util.TreeMap.rotateLeft(TreeMap.java:2060)
at java.util.TreeMap.fixAfterInsertion(TreeMap.java:2127)
at java.util.TreeMap.put(TreeMap.java:574)
at java.util.TreeSet.add(TreeSet.java:255)
at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.addTimestamp(TransactionScopedTest.java:88)
at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.testTxAssociationChange(TransactionScopedTest.java:104)
at com.hp.mwtests.ts.jta.cdi.transactionScoped.TransactionScopedTest.access$000(TransactionScopedTest.java:54)
Running com.hp.mwtests.ts.jta.cdi.transactional.TransactionalImplTest
Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.783 sec
Results :
Tests in error:
TransactionScopedTest.testTxAssociationChangeConcurrently:179 Concurrent test...
Tests run: 28, Failures: 0, Errors: 1, Skipped: 0
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2028) Three minor findbugs issues in JTA cdi module
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2028:
--------------------------------------
Summary: Three minor findbugs issues in JTA cdi module
Key: JBTM-2028
URL: https://issues.jboss.org/browse/JBTM-2028
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA
Affects Versions: 5.0.0.CR1
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.CR2
[INFO] Incorrect lazy initialization of static field com.arjuna.ats.jta.cdi.TransactionContext.transactionManager in com.arjuna.ats.jta.cdi.TransactionContext.getTransactionManager() ["com.arjuna.ats.jta.cdi.TransactionContext"] At TransactionContext.java:[lines 44-159]
[INFO] Incorrect lazy initialization of static field com.arjuna.ats.jta.cdi.TransactionContext.transactionSynchronizationRegistry in com.arjuna.ats.jta.cdi.TransactionContext.getTransactionSynchronizationRegistry() ["com.arjuna.ats.jta.cdi.TransactionContext"] At TransactionContext.java:[lines 44-159]
[INFO] Class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase defines non-transient non-serializable instance field beanManager ["com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase"] At TransactionalInterceptorBase.java:[lines 45-170]
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2026) Error when invoking @Remove method for stateful bean in transaction
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2026?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2026:
-------------------------------------
Hi,
I think you have arrived at the wrong place sorry. This looks an issue in the application server rather than the transaction manager. You could try over: https://issues.jboss.org/browse/WFLY
(Component is EJB)
Hope that helps,
Tom
> Error when invoking @Remove method for stateful bean in transaction
> -------------------------------------------------------------------
>
> Key: JBTM-2026
> URL: https://issues.jboss.org/browse/JBTM-2026
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: noel a.a
> Assignee: Tom Jenkinson
> Priority: Blocker
>
> I'm invoking method annotated with @Remove
> @Remove
> public void remove() {
> ...
> On invocation inside active transaction I'm getting following error :
> Caused by: java.lang.IllegalStateException: ARJUNA016082: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:374)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:351)
> at org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.destroyInstance(TransactionAwareObjectFactory.java:66) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:165) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:57) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:100) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:39) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.removeSession(StatefulSessionComponent.java:283) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulRemoveInterceptor.processInvocation(StatefulRemoveInterceptor.java:100) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:200) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> ... 140 more
> EJB Spec paragraphe 4.6.4 states:
> If a session bean instance is participating in a transaction, it is an error for a client to invoke the remove method on the session object’s home or component interface object. The container must detect such an attempt and throw the javax.ejb.RemoveException to the client. The container should not mark the client’s transaction for rollback, thus allowing the client to recover. Note that this restriction only applies to the remove method on the session object’s home or component interface, not to the invocation of @Remove methods.
--
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
10 years, 6 months
[JBoss JIRA] (JBTM-2026) Error when invoking @Remove method for stateful bean in transaction
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2026?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2026.
-------------------------------
Resolution: Migrated to another ITS
> Error when invoking @Remove method for stateful bean in transaction
> -------------------------------------------------------------------
>
> Key: JBTM-2026
> URL: https://issues.jboss.org/browse/JBTM-2026
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: noel a.a
> Assignee: Tom Jenkinson
> Priority: Blocker
>
> I'm invoking method annotated with @Remove
> @Remove
> public void remove() {
> ...
> On invocation inside active transaction I'm getting following error :
> Caused by: java.lang.IllegalStateException: ARJUNA016082: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:374)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:351)
> at org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.destroyInstance(TransactionAwareObjectFactory.java:66) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:165) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:57) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:100) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:39) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.removeSession(StatefulSessionComponent.java:283) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulRemoveInterceptor.processInvocation(StatefulRemoveInterceptor.java:100) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:200) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
> ... 140 more
> EJB Spec paragraphe 4.6.4 states:
> If a session bean instance is participating in a transaction, it is an error for a client to invoke the remove method on the session object’s home or component interface object. The container must detect such an attempt and throw the javax.ejb.RemoveException to the client. The container should not mark the client’s transaction for rollback, thus allowing the client to recover. Note that this restriction only applies to the remove method on the session object’s home or component interface, not to the invocation of @Remove methods.
--
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
10 years, 6 months