November 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3193) RTS benchmarks do not run

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3193?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-3193: -------------------------------------- Assignee: Michael Musgrove (was: Thomas Jenkinson) > RTS benchmarks do not run > ------------------------- > > Key: JBTM-3193 > URL: https://issues.jboss.org/browse/JBTM-3193 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > > There looks to be a JTA record in the object store when they are run. Could it be from a previous run? Or is it expected and if so why is the RecordManager unaware of the JTA_RECORD type for this run due to https://github.com/jbosstm/narayana/blob/1e17caa16b5efb9b16cdb2d8489a1b93... not being triggered? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3196) Upgrade to Artemis version 2.9.0

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3196?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3196. ---------------------------------- Resolution: Done > Upgrade to Artemis version 2.9.0 > -------------------------------- > > Key: JBTM-3196 > URL: https://issues.jboss.org/browse/JBTM-3196 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Build System > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.10.0.Final > > > The version in WildFly is 2.9.0 currently: https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/pom.xml#L297 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3196) Upgrade to Artemis version 2.9.0

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3196?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3196: ----------------------------------- Fix Version/s: 5.10.0.Final > Upgrade to Artemis version 2.9.0 > -------------------------------- > > Key: JBTM-3196 > URL: https://issues.jboss.org/browse/JBTM-3196 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Build System > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.10.0.Final > > > The version in WildFly is 2.9.0 currently: https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/pom.xml#L297 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3202) org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single failed: user id '' is too big

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3202?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3202. ---------------------------------- Resolution: Done > org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single failed: user id '' is too big > ----------------------------------------------------------------------------------------- > > Key: JBTM-3202 > URL: https://issues.jboss.org/browse/JBTM-3202 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.10.0.Final > > > On certain machines this can happen building the blacktie assembly -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3202) org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single failed: user id '' is too big

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3202?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3202: ----------------------------------- Fix Version/s: 5.10.0.Final > org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single failed: user id '' is too big > ----------------------------------------------------------------------------------------- > > Key: JBTM-3202 > URL: https://issues.jboss.org/browse/JBTM-3202 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.10.0.Final > > > On certain machines this can happen building the blacktie assembly -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3205) Spring Boot + JAX-RS support

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/JBTM-3205?page=com.atlassian.jira.plugin.... ] Matej Kralik commented on JBTM-3205: ------------------------------------ [~mmusgrov] Thanks, I will try it as soon as possible. After that, I can provide one service (same as hotel service in the quickstart) to the quickstart which using Spring Boot + JAX RS for demonstrating the purpose of this use case. I mean it that the quickstart in the /rts/lra will use the same services. Only the hotel service can be replaced by the hotel Spring service if a user wants to try it. (let's say that service would be in /rts/lra/springbootsupport folder) > Spring Boot + JAX-RS support > ---------------------------- > > Key: JBTM-3205 > URL: https://issues.jboss.org/browse/JBTM-3205 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Major > > I created this enhancement for tracking all issues for Spring Boot + JAX-RS application. > {code:xml} > ... > <parent> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-parent</artifactId> > <version>2.1.6.RELEASE</version> > <relativePath/>  > </parent> > ... > <dependencies> >  > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-jersey</artifactId> > </dependency> > ... > </dependencies> > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3205) Spring Boot + JAX-RS support

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3205?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3205: ---------------------------------------- [~mkralik] I have resolved both blocking issues for this task and the fixes are on master (github.com/jbosstm/narayana). Many apologies for taking so long to get them fixed. If you find more issues I/we will commit to getting them resolved in a more timely fashion. Will you let us know when you have retested your code so that we can mark this JIRA as resolved. Thanks > Spring Boot + JAX-RS support > ---------------------------- > > Key: JBTM-3205 > URL: https://issues.jboss.org/browse/JBTM-3205 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Major > > I created this enhancement for tracking all issues for Spring Boot + JAX-RS application. > {code:xml} > ... > <parent> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-parent</artifactId> > <version>2.1.6.RELEASE</version> > <relativePath/>  > </parent> > ... > <dependencies> >  > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-jersey</artifactId> > </dependency> > ... > </dependencies> > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3206) StringIndexOutOfBoundsException in Spring Boot JAX-RS

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3206?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3206: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > StringIndexOutOfBoundsException in Spring Boot JAX-RS > ----------------------------------------------------- > > Key: JBTM-3206 > URL: https://issues.jboss.org/browse/JBTM-3206 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Attachments: flight_5.9.6.zip > > > I have two same services (flight from the lra quickstart). One is original, another is Spring Boot with JAX-RS endpoint. > The service is sitting on the root path {code:java} http://localhost:8083 {code} > When I run the Spring Boot application and call the endpoint, the error is thrown: > {code:java} > 2019-10-02 10:21:02.944 ERROR 8482 --- [nio-8083-exec-4] o.a.c.c.C.[.[.[.[.m.t.f.JerseyConfig] : Servlet.service() for servlet [org.mkralik.testing.flight.JerseyConfig] in context with path [] threw exception [java.lang.StringIndexOutOfBoundsException: String index out of range: -1] with root cause > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1967) ~[na:1.8.0_222] > at io.narayana.lra.client.NarayanaLRAClient.getTerminationUris(NarayanaLRAClient.java:398) ~[lra-client-5.9.6.Final.jar!/:5.9.6.Final] > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:301) ~[lra-filters-5.9.6.Final.jar!/:5.9.6.Final] > at org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:132) ~[jersey-server-2.27.jar!/:na] > at org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:68) ~[jersey-server-2.27.jar!/:na] > at org.glassfish.jersey.process.internal.Stages.process(Stages.java:197) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:269) ~[jersey-server-2.27.jar!/:na] > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:272) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:268) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.internal.Errors.process(Errors.java:268) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:289) ~[jersey-common-2.27.jar!/:na] > at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:256) ~[jersey-server-2.27.jar!/:na] > at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703) ~[jersey-server-2.27.jar!/:na] > at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:416) ~[jersey-container-servlet-core-2.27.jar!/:na] > at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:370) ~[jersey-container-servlet-core-2.27.jar!/:na] > at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:389) ~[jersey-container-servlet-core-2.27.jar!/:na] > at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:342) ~[jersey-container-servlet-core-2.27.jar!/:na] > at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:229) ~[jersey-container-servlet-core-2.27.jar!/:na] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) ~[spring-web-5.1.8.RELEASE.jar!/:5.1.8.RELEASE] > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar!/:5.1.8.RELEASE] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200) ~[spring-web-5.1.8.RELEASE.jar!/:5.1.8.RELEASE] > at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar!/:5.1.8.RELEASE] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) ~[tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:853) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1587) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_222] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_222] > at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.21.jar!/:9.0.21] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222] > {code} > I noticed that when I call the endpoint the method [containerRequestContext.getUriInfo().getPath()|https://github.com/jbosstm...] returns: > * For original Thorntail service : "/" > * For service in Attachment SpringBoot + JAX RS: "" > That causes that with empty string, the [getTerminationUris|https://github.com/jbosstm/narayana/blob/master/rts/lr...] method fail on _StringIndexOutOfBoundsException_. > I attached the project with Narayana 5.9.6 due to [JBTM-3161|https://issues.jboss.org/browse/JBTM-3161] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3217) Take Compensate and Complete timeout information from the LRA annotation in the same class

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3217?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3217: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.jboss.org/browse/JBTM-3217 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update the handling of timeout information for Compensate and Complete according to the specification. Now it's defined in the LRA annotation similarly as for the new LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3217) Take Compensate and Complete timeout information from the LRA annotation in the same class

by Anonymous (Jira)

[ https://issues.jboss.org/browse/JBTM-3217?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Martin Stefanko created pull request #1526 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.jboss.org/browse/JBTM-3217 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update the handling of timeout information for Compensate and Complete according to the specification. Now it's defined in the LRA annotation similarly as for the new LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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