February 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2995: -------------------------------------- Summary: RTS InboundBridgeRecoveryTestCase hanging Key: JBTM-2995 URL: https://issues.jboss.org/browse/JBTM-2995 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Affects Versions: 5.7.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Critical Fix For: 5.next The following test is hanging: org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l ocal: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.<init>(ServerControl.java:223) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:71) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(TransactionImple.java:77) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.<init>(JBossLocalTransactionProvider.java:85) at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.<init>(JBossJTALocalTransactionProvider.java:52) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager .getPOA(ORBManager.java:97) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2994: -------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Stuart Douglas Resolution: Done > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Stuart Douglas created pull request #1284 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged

by Stuart Douglas (JIRA)

Stuart Douglas created JBTM-2994: ------------------------------------ Summary: TransactionExtension uses old version of addAnnotatedType which results in warnings being logged Key: JBTM-2994 URL: https://issues.jboss.org/browse/JBTM-2994 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Stuart Douglas 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2969) Make the CDI checker a standalone tool or/and mvn plugin

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2969?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1283 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make the CDI checker a standalone tool or/and mvn plugin > -------------------------------------------------------- > > Key: JBTM-2969 > URL: https://issues.jboss.org/browse/JBTM-2969 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > The way how the checker works now (as CDI extension, needed to be packed inside of the app) is not a good approach and it should work as a standalone tool or better as a maven plugin to verify the annotation in a defined phase. > The current approach needs to be reworked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka edited comment on JBTM-2993 at 2/14/18 5:20 AM: ---------------------------------------------------------------- I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log {{lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log}} with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? {{sed 's|</waitForInterrupt>|</waitForInterrupt><waitAfterLaunch>120</waitAfterLaunch>|' -i lra-test/pom.xml}} was (Author: ochaloup): I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log `lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log` with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? `sed 's|</waitForInterrupt>|</waitForInterrupt><waitAfterLaunch>120</waitAfterLaunch>|' -i lra-test/pom.xml` > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2993: --------------------------------------- I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log `lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log` with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? `sed 's|</waitForInterrupt>|</waitForInterrupt><waitAfterLaunch>120</waitAfterLaunch>|' -i lra-test/pom.xml` > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2992: ----------------------------------- Assignee: Amos Feng (was: Ondra Chaloupka) > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Critical > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependenc...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar

by Oliver Gondza (JIRA)

[ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.... ] Oliver Gondza commented on JBTM-2992: ------------------------------------- Have a look at https://github.com/olivergondza/maven-jdk-tools-wrapper, it attempts to shield users from some of that madness. > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Priority: Critical > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependenc...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.... ] Michal Karm Babacek updated JBTM-2993: -------------------------------------- Workaround Description: {code}sed -i 's/<module>lra-test<\/module>/<\!--<module>lra-test<\/module>-->/g' ./rts/lra/pom.xml{code} Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 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 February 2018