September 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3192) LRA quickstarts cannot compile

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3192?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson commented on JBTM-3192: ---------------------------------------- Thanks [~mstefank], I would just point out that I wouldn't describe this as a "cannot compile" error. It is an NPE IIUC? I think the full errors look more like: {code} [0m[31m2019-09-16 05:17:55,214 ERROR [io.narayana.lra] (default task-1) LRA025005: Error on contacting the LRA coordinator 'http://localhost:8081/lra-coordinator': javax.ws.rs.WebApplicationException: HTTP 500 Internal Server Error at io.narayana.lra.client.NarayanaLRAClient.throwGenericLRAException(NarayanaLRAClient.java:848) at io.narayana.lra.client.NarayanaLRAClient.startLRA(NarayanaLRAClient.java:293) at io.narayana.lra.filter.ServerLRAFilter.startLRA(ServerLRAFilter.java:490) at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:236) at io.narayana.lra.filter.ServerLRAFilter$Proxy$_$$_WeldClientProxy.filter(Unknown Source) at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:306) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:372) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:344) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:317) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:440) at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229) at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135) at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:356) at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.swarm.generated.FaviconErrorHandler.handleRequest(FaviconErrorHandler.java:61) at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:94) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) at java.lang.Thread.run(Thread.java:748) [0mError to contact (POST) 'http://localhost:8084/?hotelName=TheGrand&flightNumber1=BA123&flightNumbe...', error: flight booking problem [WARNING] java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:889) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3005) at TripClient.bookTrip(TripClient.java:88) at TripClient.main(TripClient.java:48) {code} Thanks for the PR I will take a look! > LRA quickstarts cannot compile > ------------------------------ > > Key: JBTM-3192 > URL: https://issues.jboss.org/browse/JBTM-3192 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > when running [/rts/lra|https://github.com/jbosstm/quickstart/tree/master/rts/lra] with {{mvn clean install}} or {{run.sh}} script both fail with: > {code:java} > Caused by: java.lang.NullPointerException > at com.fasterxml.jackson.core.JsonFactory.createParser (JsonFactory.java:889) > at com.fasterxml.jackson.databind.ObjectMapper.readValue (ObjectMapper.java:3005) > at TripClient.bookTrip (TripClient.java:89) > at TripClient.main (TripClient.java:48) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) > at java.lang.Thread.run (Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3192) LRA quickstarts cannot compile

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3192?page=com.atlassian.jira.plugin.... ] Martin Stefanko commented on JBTM-3192: --------------------------------------- The issue is caused by [this line|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordina...] where when the compensatorLink is empty String the participant lookup fails down the line which results into 412 status code being returned from the joinLRA operation of the nested LRA in the quickstart. > LRA quickstarts cannot compile > ------------------------------ > > Key: JBTM-3192 > URL: https://issues.jboss.org/browse/JBTM-3192 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > when running [/rts/lra|https://github.com/jbosstm/quickstart/tree/master/rts/lra] with {{mvn clean install}} or {{run.sh}} script both fail with: > {code:java} > Caused by: java.lang.NullPointerException > at com.fasterxml.jackson.core.JsonFactory.createParser (JsonFactory.java:889) > at com.fasterxml.jackson.databind.ObjectMapper.readValue (ObjectMapper.java:3005) > at TripClient.bookTrip (TripClient.java:89) > at TripClient.main (TripClient.java:48) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) > at java.lang.Thread.run (Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3192) LRA quickstarts cannot compile

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3192?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3192: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1500 > LRA quickstarts cannot compile > ------------------------------ > > Key: JBTM-3192 > URL: https://issues.jboss.org/browse/JBTM-3192 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > when running [/rts/lra|https://github.com/jbosstm/quickstart/tree/master/rts/lra] with {{mvn clean install}} or {{run.sh}} script both fail with: > {code:java} > Caused by: java.lang.NullPointerException > at com.fasterxml.jackson.core.JsonFactory.createParser (JsonFactory.java:889) > at com.fasterxml.jackson.databind.ObjectMapper.readValue (ObjectMapper.java:3005) > at TripClient.bookTrip (TripClient.java:89) > at TripClient.main (TripClient.java:48) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) > at java.lang.Thread.run (Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3192) LRA quickstarts cannot compile

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3192: ------------------------------------- Summary: LRA quickstarts cannot compile Key: JBTM-3192 URL: https://issues.jboss.org/browse/JBTM-3192 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.9.8.Final Reporter: Martin Stefanko Assignee: Martin Stefanko when running [/rts/lra|https://github.com/jbosstm/quickstart/tree/master/rts/lra] with {{mvn clean install}} or {{run.sh}} script both fail with: {code:java} Caused by: java.lang.NullPointerException at com.fasterxml.jackson.core.JsonFactory.createParser (JsonFactory.java:889) at com.fasterxml.jackson.databind.ObjectMapper.readValue (ObjectMapper.java:3005) at TripClient.bookTrip (TripClient.java:89) at TripClient.main (TripClient.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) at java.lang.Thread.run (Thread.java:748) {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3191) Align LRA client expectations for LRA coordinator default port

by Anonymous (Jira)

[ https://issues.jboss.org/browse/JBTM-3191?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Martin Stefanko created pull request #1499 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Align LRA client expectations for LRA coordinator default port > -------------------------------------------------------------- > > Key: JBTM-3191 > URL: https://issues.jboss.org/browse/JBTM-3191 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > LRA coordinator by default starts at port 8080, however, LRA client expects it by default at 8082. This force even very simple applications to specify {{lra.http.port}} which seems unnecessary. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3191) Align LRA client expectations for LRA coordinator default port

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3191: ------------------------------------- Summary: Align LRA client expectations for LRA coordinator default port Key: JBTM-3191 URL: https://issues.jboss.org/browse/JBTM-3191 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.9.8.Final Reporter: Martin Stefanko Assignee: Martin Stefanko LRA coordinator by default starts at port 8080, however, LRA client expects it by default at 8082. This force even very simple applications to specify {{lra.http.port}} which seems unnecessary. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3145) LRA TCK test failure on CI

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3145?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3145: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA TCK test failure on CI > -------------------------- > > Key: JBTM-3145 > URL: https://issues.jboss.org/browse/JBTM-3145 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > The test TckTests#timeLimit fails every time on the JDK 11 CI run (but not on JDK 8). For example > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/426/PROFILE=LRA,j... > It is also failing consistently on JDK8 (after the the migration to thorntail) with: > [INFO] [lra-coordinator-it-test] 2019-06-06 20:19:46,751 WARN [org.jboss.resteasy.resteasy_jaxrs.i18n] (ForkJoinPool.commonPool-worker-26) RESTEASY002120: ClassNotFoundException: Unable to load builtin provider org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from jar:file:/tmp/thorntailresteasy-jaxb-provider-3.6.2.Final3540226414131235050.jar!/META-INF/services/javax.ws.rs.ext.Providers: java.lang.ClassNotFoundException: org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3190) Transform LRA coordinator runtime to Quarkus

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3190: ------------------------------------- Summary: Transform LRA coordinator runtime to Quarkus Key: JBTM-3190 URL: https://issues.jboss.org/browse/JBTM-3190 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.9.8.Final Reporter: Martin Stefanko [LRA coordinator|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-c...] is an essential part of Narayana LRA processing. It would be beneficial to move the runtime from [Thorntail|https://thorntail.io] to [Quarkus|https://quarkus.io] for faster startup times and better memory utilization. If possible, one additional step can be to compile lra-coordinator to the native executable which can bump out the performance of the lra-coordinator docker image. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3145) LRA TCK test failure on CI

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3145?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1498 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > LRA TCK test failure on CI > -------------------------- > > Key: JBTM-3145 > URL: https://issues.jboss.org/browse/JBTM-3145 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > The test TckTests#timeLimit fails every time on the JDK 11 CI run (but not on JDK 8). For example > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/426/PROFILE=LRA,j... > It is also failing consistently on JDK8 (after the the migration to thorntail) with: > [INFO] [lra-coordinator-it-test] 2019-06-06 20:19:46,751 WARN [org.jboss.resteasy.resteasy_jaxrs.i18n] (ForkJoinPool.commonPool-worker-26) RESTEASY002120: ClassNotFoundException: Unable to load builtin provider org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from jar:file:/tmp/thorntailresteasy-jaxb-provider-3.6.2.Final3540226414131235050.jar!/META-INF/services/javax.ws.rs.ext.Providers: java.lang.ClassNotFoundException: org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3189) Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3189: -------------------------------------- Summary: Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA Key: JBTM-3189 URL: https://issues.jboss.org/browse/JBTM-3189 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.8.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next When an LRA is cancelled from a timer the cancellation is performed by a thread from the ForkJoinPool. None of the Resteasy JAX-RS providers are available on this thread. Outgoing JAX-RS calls made from this thread will then fail. Since the LRA coordinator only uses REST calls it would be better to use something like java.net.HttpURLConnection or wait for java.net.http.HttpClient which is in JDK 11. But as an interim fix I would suggest that the timeout handler sets the status to Cancelling and then when the LRA is later closed we check whether the timer triggered and cancel the LRA. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 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 September 2019