February 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3086) dependentLRA test failure

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3086: -------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/...] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/sr...] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3089) LRA code improvements

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3089?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3089: -------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > LRA code improvements > --------------------- > > Key: JBTM-3089 > URL: https://issues.jboss.org/browse/JBTM-3089 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Remove TODO comments from the code and replace with JIRA issues. > Ensure that the message string in all occurrences of GenericLRAException are meaningful. > Remove all commented out pieces of code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3090?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3090: -------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > LRA TCK failures need to report more context to facilitate debugging > -------------------------------------------------------------------- > > Key: JBTM-3090 > URL: https://issues.jboss.org/browse/JBTM-3090 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test failure message reports > > failures.forEach(f -> System.out.printf("%s%n", f)); > where f is the failure reason. There is also a verbose option which prints out the stack trace where the failure was reported. But in some failure cases these two pieces of information are insufficient to debug the failure. It would be nice if the resources that participated in the test also logged information which could be reported for more effective analysis of the reasons for the failure. This last requirement may affect the TCK itself so the code in the eclipse microprofile-lra repo should be analysed as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3093) Disable the maven site plugin for the LRA module

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3093: -------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > Disable the maven site plugin for the LRA module > ------------------------------------------------ > > Key: JBTM-3093 > URL: https://issues.jboss.org/browse/JBTM-3093 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The narayana code coverage profile invokes the maven site goal so that the output can be viewed easily. > > Now LRA relies on microprofile-lra-api snapshot builds but the site plugin appears to resolve to the latest snapshot (rather than a particular snapshot build) and since microprofile-lra-api regularly undergoes changes there are compilation failures. > This JIRA proposes that we disable the site plugin for the LRA module. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3105) STM TaxonomyTest failure

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3105?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3105: -------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > STM TaxonomyTest failure > ------------------------ > > Key: JBTM-3105 > URL: https://issues.jboss.org/browse/JBTM-3105 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There was test failure during a CI PR test: testIsClosedNestedParentNotVisible(org.jboss.stm.TaxonomyTest) on job > http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-cately... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3091) LRA module should depend on a specific snapshot build

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3091. ------------------------------- > LRA module should depend on a specific snapshot build > ----------------------------------------------------- > > Key: JBTM-3091 > URL: https://issues.jboss.org/browse/JBTM-3091 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > The current implementation was coded against the following maven snapshot: > org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3113) LRA coordinator defines in depenedencies whole microprofile stack

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3113?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3113: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1408 > LRA coordinator defines in depenedencies whole microprofile stack > ----------------------------------------------------------------- > > Key: JBTM-3113 > URL: https://issues.jboss.org/browse/JBTM-3113 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The LRA coordinator defines the depenendency on whole MicroProfile stack. That's not necessary as it uses JAX-RS and CDI. The depenencies needed up to that will be resolved by the Wfly Swarm/Thorntail runtime. If we define whole stack then Wfly Swarm loads to the runtime unnecessary dependencies which makes the fat jar bigger than it needs to be. Plus the start time the container could be lower when we use only the dependencies which are really needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3113) LRA coordinator defines in depenedencies whole microprofile stack

by Ondra Chaloupka (Jira)

Ondra Chaloupka created JBTM-3113: ------------------------------------- Summary: LRA coordinator defines in depenedencies whole microprofile stack Key: JBTM-3113 URL: https://issues.jboss.org/browse/JBTM-3113 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.2.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka The LRA coordinator defines the depenendency on whole MicroProfile stack. That's not necessary as it uses JAX-RS and CDI. The depenencies needed up to that will be resolved by the Wfly Swarm/Thorntail runtime. If we define whole stack then Wfly Swarm loads to the runtime unnecessary dependencies which makes the fat jar bigger than it needs to be. Plus the start time the container could be lower when we use only the dependencies which are really needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3112) Remove dependency on LRA client from LRA coordinator

by Anonymous (Jira)

[ https://issues.jboss.org/browse/JBTM-3112?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Martin Stefanko created pull request #1412 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Remove dependency on LRA client from LRA coordinator > ---------------------------------------------------- > > Key: JBTM-3112 > URL: https://issues.jboss.org/browse/JBTM-3112 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > LRA coordinator should not depend on LRA client as these services should be able to operate independently (as separate microservices deployments). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3110) JNDIBean CDI Deployment Failure

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3110?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3110: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JNDIBean CDI Deployment Failure > ------------------------------- > > Key: JBTM-3110 > URL: https://issues.jboss.org/browse/JBTM-3110 > Project: JBoss Transaction Manager > Issue Type: Bug > Environment: Wildfly 16 Beta 1 > Reporter: Cody Lerum > Assignee: Matej Novotny > Priority: Major > Fix For: 5.9.1.Final > > > While testing Wildfly 16.0.0.Beta1 with an existing working (Wildfly 14.0.1) project we were unable to deploy the war as weld threw an exception. > {code} > org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001477: The bean Managed Bean [class co.cfly.oss.lerg.rateCenter.inventoryRequest.InventoryRequestView] with qualifiers [@Default @Any @Named] declares a passivating scope but has a(n) Interceptor [class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired intercepts @Transactional] with a non-passivation-capable dependency com.arjuna.ats.jta.cdi.JNDIBean@12e2cb9f > at org.jboss.weld.bootstrap.Validator.validateInterceptorDecoratorInjectionPointPassivationCapable(Validator.java:480) > at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:225) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} > I opened WFLY-11716 and had [~manovotn] take a look. The issue is due to the JNDIBean not implementing PassivationCapable. He has also added a suggested fix in the issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 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 2019