November 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2026) Error when invoking @Remove method for stateful bean in transaction

by noel a.a (JIRA)

noel a.a created JBTM-2026: ------------------------------ Summary: 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2025) Update to Maven 3.1.0

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2025?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2025: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/532 > Update to Maven 3.1.0 > --------------------- > > Key: JBTM-2025 > URL: https://issues.jboss.org/browse/JBTM-2025 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.CR2 > > > WildFly has updated its build system to 3.1.0. As we have a subsystem that inherits from their parent it is causing a build failure. We should upgrade to 3.1.0 to match their expectations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2025) Update to Maven 3.1.1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2025?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2025: -------------------------------- Summary: Update to Maven 3.1.1 (was: Update to Maven 3.1.0) > Update to Maven 3.1.1 > --------------------- > > Key: JBTM-2025 > URL: https://issues.jboss.org/browse/JBTM-2025 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.CR2 > > > WildFly has updated its build system to 3.1.0. As we have a subsystem that inherits from their parent it is causing a build failure. We should upgrade to 3.1.0 to match their expectations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2025) Update to Maven 3.1.1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2025?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2025: ------------------------------------- This is the wildfly commit: https://github.com/wildfly/wildfly/commit/4ce7958b65f9bbd89327d286cc17ad5... > Update to Maven 3.1.1 > --------------------- > > Key: JBTM-2025 > URL: https://issues.jboss.org/browse/JBTM-2025 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.CR2 > > > WildFly has updated its build system to 3.1.0. As we have a subsystem that inherits from their parent it is causing a build failure. We should upgrade to 3.1.0 to match their expectations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-2025) Update to Maven 3.1.0

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2025: ----------------------------------- Summary: Update to Maven 3.1.0 Key: JBTM-2025 URL: https://issues.jboss.org/browse/JBTM-2025 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.CR2 WildFly has updated its build system to 3.1.0. As we have a subsystem that inherits from their parent it is causing a build failure. We should upgrade to 3.1.0 to match their expectations. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1916) Create parallel CI job for pull requests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1916?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1916: --------------------------------- > Create parallel CI job for pull requests > ---------------------------------------- > > Key: JBTM-1916 > URL: https://issues.jboss.org/browse/JBTM-1916 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1916) Create parallel CI job for pull requests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1916?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1916: -------------------------------- Fix Version/s: 4.17.17 > Create parallel CI job for pull requests > ---------------------------------------- > > Key: JBTM-1916 > URL: https://issues.jboss.org/browse/JBTM-1916 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5, 4.17.17 > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1916) Create parallel CI job for pull requests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1916?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1916. --------------------------------- Resolution: Done > Create parallel CI job for pull requests > ---------------------------------------- > > Key: JBTM-1916 > URL: https://issues.jboss.org/browse/JBTM-1916 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.17, 5.0.0.M5 > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1916) Create parallel CI job for pull requests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1916?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1916. ------------------------------- > Create parallel CI job for pull requests > ---------------------------------------- > > Key: JBTM-1916 > URL: https://issues.jboss.org/browse/JBTM-1916 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5, 4.17.17 > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1900) Add test profiles to narayana.sh

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1900?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1900: -------------------------------- Fix Version/s: 4.17.17 > Add test profiles to narayana.sh > -------------------------------- > > Key: JBTM-1900 > URL: https://issues.jboss.org/browse/JBTM-1900 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5, 4.17.17 > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Take example from narayana multi-job: > {code} > if [ "$TESTS" == "MAIN" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 RTS_AS_TESTS=1 RTS_TESTS=1 JTA_CDI_TESTS=1 TXF_TESTS=0 XTS_TESTS=0 XTS_AS_TESTS=0 txbridge=0 QA_TESTS=0 BLACKTIE=0 > elif [ "$TESTS" == "XTS" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 JTA_CDI_TESTS=0 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=0 BLACKTIE=0 > elif [ "$TESTS" == "QA_JTA" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 JTA_CDI_TESTS=0 TXF_TESTS=0 XTS_TESTS=0 XTS_AS_TESTS=0 txbridge=0 QA_TESTS=1 SUN_ORB=1 JAC_ORB=0 QA_TARGET=ci-tests-nojts BLACKTIE=0 > elif [ "$TESTS" == "QA_JTS_JACORB" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 JTA_CDI_TESTS=0 TXF_TESTS=0 XTS_TESTS=0 XTS_AS_TESTS=0 txbridge=0 QA_TESTS=1 SUN_ORB=0 JAC_ORB=1 QA_TARGET=ci-jts-tests BLACKTIE=0 > elif [ "$TESTS" == "QA_JTS_JDKORB" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 JTA_CDI_TESTS=0 TXF_TESTS=0 XTS_TESTS=0 XTS_AS_TESTS=0 txbridge=0 QA_TESTS=1 SUN_ORB=1 JAC_ORB=0 QA_TARGET=ci-jts-tests BLACKTIE=0 > elif [ "$TESTS" == "BLACKTIE" ]; then > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 JTA_CDI_TESTS=0 TXF_TESTS=0 XTS_TESTS=0 XTS_AS_TESTS=0 txbridge=0 QA_TESTS=0 BLACKTIE=1 > if [ "$label" == "linux64el5" ]; then > export SKIP_VALGRIND=-Duse.valgrind=false > fi > fi > {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

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2013