April 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3293) LRA coordinator jar cannot be deployed on WildFly

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3293?page=com.atlassian.jira.plugin... ] Martin Stefanko commented on JBTM-3293: --------------------------------------- It seems that the Weld is not correctly processing the loaded classes and log is filled with errors like this: {noformat} 15:45:49,524 WARN [org.jboss.modules.define] (Weld Thread Pool -- 1) Failed to define class io.narayana.lra.coordinator.internal.LRACompensatorMap in Module "deployment.lra-coordinator.jar" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link io/narayana/lra/coordinator/internal/LRACompensatorMap (Module "deployment.lra-coordinator.jar" from Service Module Loader): com/arjuna/ats/arjuna/coordinator/abstractrecord/RecordTypeMap at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1095) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:424) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:731) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at org.jboss.as.weld@20.0.0.Beta1-SNAPSHOT//org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.AnnotatedTypeLoader.loadClass(AnnotatedTypeLoader.java:82) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.AnnotatedTypeLoader.loadAnnotatedType(AnnotatedTypeLoader.java:62) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.FastAnnotatedTypeLoader.loadAnnotatedType(FastAnnotatedTypeLoader.java:108) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:87) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:55) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:52) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) at org.jboss.weld.core@3.1.4.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) 15:45:49,525 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-000119: Not generating any bean definitions from io.narayana.lra.coordinator.internal.LRACompensatorMap because of underlying class loading error: Type Failed to link io.narayana.lra.coordinator.internal.LRACompensatorMap (Module "deployment.lra-coordinator.jar" from Service Module Loader): com.arjuna.ats.arjuna.coordinator.abstractrecord.RecordTypeMap not found. If this is unexpected, enable DEBUG logging to see the full error. {noformat} which seems similar to https://issues.redhat.com/browse/WFLY-5720. Just changing the packaging to war fixes all the issues. So it seems that if we want to have LRA coordinator available as a deployable web application we should include a new module lra-coordinator-war which will be packaging lra-coordinator-jar as a WAR archive. [~mmusgrov], [~ochaloup] WDYT? > LRA coordinator jar cannot be deployed on WildFly > ------------------------------------------------- > > Key: JBTM-3293 > URL: https://issues.redhat.com/browse/JBTM-3293 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > I am not sure whether this should be possible but the lra-coordinator.jar from lra-coordinator-jar module can't be deployed on latest WildFly. The deployment fails with the following error: > {noformat} > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type LRAService with qualifiers @Default > at injection point [BackedAnnotatedField] @Inject io.narayana.lra.coordinator.api.RecoveryCoordinator.lraService > at io.narayana.lra.coordinator.api.RecoveryCoordinator.lraService(RecoveryCoordinator.java:0) > WELD-001474: Class io.narayana.lra.coordinator.domain.service.LRAService is on the classpath, but was ignored because a class it references was not found: com.arjuna.ats.arjuna.recovery.RecoveryModule from [Module "deployment.lra-coordinator.jar" from Service Module Loader]. > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3287) ThornTail LRA coordinator cannot start

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3287?page=com.atlassian.jira.plugin... ] Michael Musgrove edited comment on JBTM-3287 at 4/20/20 6:56 AM: ----------------------------------------------------------------- [~ochaloup] That explanation was very helpful. But the only way I can run the thorntail based coordinator is to explicitly change the pom to depend on the -RC1 version (like you suggested). But does this mean we should reopen this JIRA? [update] I retested starting the coordinator and it starts fine. I am not sure why I could not start it last week. So please ignore my comment. was (Author: mmusgrov): [~ochaloup] That explanation was very helpful. But the only way I can run the thorntail based coordinator is to explicitly change the pom to depend on the -RC1 version (like you suggested). But does this mean we should reopen this JIRA? > ThornTail LRA coordinator cannot start > -------------------------------------- > > Key: JBTM-3287 > URL: https://issues.redhat.com/browse/JBTM-3287 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > {noformat} > Caused by: java.lang.NoClassDefFoundError: org/eclipse/microprofile/lra/annotation/LRAStatus > {noformat} > It seems that the LRA API dependency needs to be defined directly in the lra-coordinator-thorntail module. It isn't picked up from transitive dependency (lra-coordinator-jar). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3291) LRA quickstart needs to work with the latest Eclipse MicroProfile LRA spec

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3291?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3291: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1603/ > LRA quickstart needs to work with the latest Eclipse MicroProfile LRA spec > -------------------------------------------------------------------------- > > Key: JBTM-3291 > URL: https://issues.redhat.com/browse/JBTM-3291 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Blocker > Fix For: 5.next > > > At least one of the LRA quickstarts [1] defines a resource that uses an LRA annotation without also being a participant. This requirement was introduced in issue [2]. > [1] trip-controller/src/main/java/io/narayana/rts/lra/demo/tripcontroller/TripController.java > [2] https://github.com/eclipse/microprofile-lra/issues/272 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3285) Reduce the number of axes on PR jobs

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3285?page=com.atlassian.jira.plugin... ] Michael Musgrove closed JBTM-3285. ---------------------------------- Resolution: Rejected This task can be implemented directly via the Jenkins UI > Reduce the number of axes on PR jobs > ------------------------------------ > > Key: JBTM-3285 > URL: https://issues.redhat.com/browse/JBTM-3285 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Our CI system runs a pull request poller which checks for new PRs by looking at the PR description to decide which Jenkins job axes to run. We have quite a few axes (QA_JTS_JACORB, QA_JTS_JDKORB, QA_JTS_OPENJDKORB, QA_JTA, XTS, CORE, BLACKTIE, RTS, mysql, postgres, db2, oracle, TOMCAT, JACOCO, LRA) and if the user, say, just wants to run the XTS axis then CI will start a job for each axis. All but the XTS axis will then check whether it needs to run and then terminate. Each axis can end up taking 20 minutes or so. It would be good to minimise this overhead. > For example, all of the QA axes could be run in one job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3291) LRA quickstart needs to work with the latest Eclipse MicroProfile LRA spec

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3291?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3291: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA quickstart needs to work with the latest Eclipse MicroProfile LRA spec > -------------------------------------------------------------------------- > > Key: JBTM-3291 > URL: https://issues.redhat.com/browse/JBTM-3291 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Blocker > Fix For: 5.next > > > At least one of the LRA quickstarts [1] defines a resource that uses an LRA annotation without also being a participant. This requirement was introduced in issue [2]. > [1] trip-controller/src/main/java/io/narayana/rts/lra/demo/tripcontroller/TripController.java > [2] https://github.com/eclipse/microprofile-lra/issues/272 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3287) ThornTail LRA coordinator cannot start

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3287?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3287: ---------------------------------------- [~ochaloup] That explanation was very helpful. But the only way I can run the thorntail based coordinator is to explicitly change the pom to depend on the -RC1 version (like you suggested). But does this mean we should reopen this JIRA? > ThornTail LRA coordinator cannot start > -------------------------------------- > > Key: JBTM-3287 > URL: https://issues.redhat.com/browse/JBTM-3287 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > {noformat} > Caused by: java.lang.NoClassDefFoundError: org/eclipse/microprofile/lra/annotation/LRAStatus > {noformat} > It seems that the LRA API dependency needs to be defined directly in the lra-coordinator-thorntail module. It isn't picked up from transitive dependency (lra-coordinator-jar). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3284) TckRecoveryTests are failing

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3284?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Martin Stefanko created pull request #1604 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > TckRecoveryTests are failing > ---------------------------- > > Key: JBTM-3284 > URL: https://issues.redhat.com/browse/JBTM-3284 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > TckRecoveryTests are failing with several issues. Also will require some fixes in the TCK. > {noformat} > [INFO] [lra-coordinator-it-test] Caused by: java.lang.NullPointerException > [INFO] [lra-coordinator-it-test] at io.narayana.lra.coordinator.domain.model.LRARecord.atEnd(LRARecord.java:443) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3295) LRACDIExtension returns null as class name when @LRA annotated class does not contain Compensate or AfterLRA

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3295?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3295: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > LRACDIExtension returns null as class name when @LRA annotated class does not contain Compensate or AfterLRA > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-3295 > URL: https://issues.redhat.com/browse/JBTM-3295 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > When the {{@LRA}} annotated class does not containe neither {{@Compensate}} nor {{@AfterLRA}} the exception message contains {{null}} instead of the name of the guilty class. > {code} > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > java.lang.IllegalStateException: null: The class contains an LRA method and no Compensate or AfterLRA method was found. > at io.narayana.lra.client.internal.proxy.nonjaxrs.LRACDIExtension.isLRAParticipant(LRACDIExtension.java:129) > at io.narayana.lra.client.internal.proxy.nonjaxrs.LRACDIExtension.getAsParticipant(LRACDIExtension.java:104) > at io.narayana.lra.client.internal.proxy.nonjaxrs.LRACDIExtension.observe(LRACDIExtension.java:75) > {code} > The reason seems to be that the method {{ClassInfo.simpleName()}} returns null if it's not an inner class or nested class. > The javadoc says following on it > {code} > Returns the source declared name of this class if it is an inner class, or a local class. Otherwise > this method will return null. > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3292) JTS Interoperability (WildFly with GlassFish) Quickstart fails

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3292?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3292: ----------------------------------- Fix Version/s: (was: 5.next) > JTS Interoperability (WildFly with GlassFish) Quickstart fails > -------------------------------------------------------------- > > Key: JBTM-3292 > URL: https://issues.redhat.com/browse/JBTM-3292 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > > The JTS Interoperability Quickstart checks interop between WildFly and GlassFish but it is failing when building the WildFly: Distribution: > {quote} > }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => { > "WFLYCTL0412: Required services that are not installed:" => ["elytron.security-properties"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.providers.elytron is missing [elytron.security-properties]"] > {quote} > It works on the latest CI run (http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/13/co...) but not on earlier ones (eg 11). So this may be something that has already been fixed and the issue can be closed as such. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3292) JTS Interoperability (WildFly with GlassFish) Quickstart fails

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3292?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka resolved JBTM-3292. ------------------------------------ Resolution: Duplicate I'm closing this as duplicate of the JBTM-3290. The issue should be (hopefully) fixed by the changeset https://github.com/jbosstm/quickstart/pull/275/files > JTS Interoperability (WildFly with GlassFish) Quickstart fails > -------------------------------------------------------------- > > Key: JBTM-3292 > URL: https://issues.redhat.com/browse/JBTM-3292 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The JTS Interoperability Quickstart checks interop between WildFly and GlassFish but it is failing when building the WildFly: Distribution: > {quote} > }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => { > "WFLYCTL0412: Required services that are not installed:" => ["elytron.security-properties"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.providers.elytron is missing [elytron.security-properties]"] > {quote} > It works on the latest CI run (http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/13/co...) but not on earlier ones (eg 11). So this may be something that has already been fixed and the issue can be closed as such. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2020