August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1715: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M5) > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.jboss.org/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1042) GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1042?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1042: ------------------------------------- Amos, Can you give me some more information on this? Also, do you have a proposed fix? > GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES) > -------------------------------------------------------------------------------------- > > Key: JBTM-1042 > URL: https://issues.jboss.org/browse/JBTM-1042 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > 1.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple Line 132 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.isParticipantPresent(Uid) > 2.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple Line 128 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple.isParticipantPresent(Uid) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1042) GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1042?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1042: -------------------------------- Assignee: Amos Feng (was: Paul Robinson) > GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES) > -------------------------------------------------------------------------------------- > > Key: JBTM-1042 > URL: https://issues.jboss.org/browse/JBTM-1042 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > 1.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple Line 132 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.isParticipantPresent(Uid) > 2.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple Line 128 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple.isParticipantPresent(Uid) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1703) @CompensationScoped does not garbage collect

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1703?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1703: ------------------------------------- Done: https://github.com/Gytis/narayana/blob/master/txframework/src/main/java/o... > @CompensationScoped does not garbage collect > -------------------------------------------- > > Key: JBTM-1703 > URL: https://issues.jboss.org/browse/JBTM-1703 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1703) @CompensationScoped does not garbage collect

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1703?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1703. --------------------------------- Resolution: Done > @CompensationScoped does not garbage collect > -------------------------------------------- > > Key: JBTM-1703 > URL: https://issues.jboss.org/browse/JBTM-1703 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1779) txframework DataManagementTest does not work under emma

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1779?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1779: ------------------------------------- TXDM doesn't apply to the new Compensations API, so the easiest thing would be to simply remove it. > txframework DataManagementTest does not work under emma > ------------------------------------------------------- > > Key: JBTM-1779 > URL: https://issues.jboss.org/browse/JBTM-1779 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > There is a single txf test that does not run correctly under emma. It complains about not being able to find vladium. > The problem appears to be that this test creates an arq deployment containing its own copy of the TXDataMap rather than trying to use the one that is deployed already in the AS and is therefore in a different classloader so can't see the shaded emma classes from the real module. > When I modify the test to remove that class and use the txf module directly, the same as all the other tests in the txf module, it can't load the TXDM class from the module. The difference is that the TXDM is injected into test beans that are injected into the tests, rather than directly injected. I think this could be a limitation of Emma. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1645: -------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Allow pull requests to configure some parameters in scripts/hudson/narayana.sh > ------------------------------------------------------------------------------ > > Key: JBTM-1645 > URL: https://issues.jboss.org/browse/JBTM-1645 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the pull description has something like this: > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests] > We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1871) Automatically add the "org.jboss.xts" dependency for XTS applications

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1871?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1871: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M5) > Automatically add the "org.jboss.xts" dependency for XTS applications > --------------------------------------------------------------------- > > Key: JBTM-1871 > URL: https://issues.jboss.org/browse/JBTM-1871 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > > At deployment time we should automatically add the org.jboss.xts dependency for applications that need it. > We should be able to detect deployments that use XTS annotations (i.e those provided by the Compensations API) through Jandex. I'm not sure how we would detect those that don't use annotations; something to investigate. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1749: ------------------------------------- Yes it does. > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: See discussion > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1749. --------------------------------- Resolution: Done > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: See discussion > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2013