March 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3123: ----------------------------------- Fix Version/s: 5.next > LRA POST to "start" has Incorrect @ApiResponse annotation > --------------------------------------------------------- > > Key: JBTM-3123 > URL: https://issues.jboss.org/browse/JBTM-3123 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Lance Ball > Assignee: Martin Stefanko > Priority: Minor > Fix For: 5.next > > > In {{java.io.narayana.lra.coordinator.api.Coordinator}} the {{@ApiResponse}} annotation [specifies a response code |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L227] of {{200}} for the "start" endpoint, however, [what is actually returned |https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator/src/main/java/io/narayana/lra/coordinator/api/Coordinator.java#L281] is {{Response.Status.CREATED}} which is HTTP code {{201}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3118) Protocol family unavailable error in lra-coordinator Docker container

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3118: ----------------------------------- Fix Version/s: 5.next > Protocol family unavailable error in lra-coordinator Docker container > --------------------------------------------------------------------- > > Key: JBTM-3118 > URL: https://issues.jboss.org/browse/JBTM-3118 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Lance Ball > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > Attempting to run the `lra-coordinator` image, it silently fails. So I started the container using this command. > ```sh > docker run --rm -it -p 8080:8080 jbosstm/lra-coordinator /bin/bash > ``` > Running the command `java -jar lra-coordinator.jar` from the `deployments` directory produces the following output before the process dies. > ```log > 2019-03-08 19:11:57,808 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: WFLYUT0082: Could not start 'default' listener. > at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:181) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > 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) > Caused by: java.net.SocketException: Protocol family unavailable > at sun.nio.ch.Net.bind0(Native Method) > at sun.nio.ch.Net.bind(Net.java:433) > at sun.nio.ch.Net.bind(Net.java:425) > at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) > at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:179) > at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:310) > at org.wildfly.extension.undertow.HttpListenerService.startListening(HttpListenerService.java:106) > at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:169) > ... 5 more > 2019-03-08 19:11:57,846 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.undertow.listener.default" => "WFLYUT0082: Could not start 'default' listener. > Caused by: java.net.SocketException: Protocol family unavailable"}} > ``` > I can successfully start the coordinator from within the container by specifying a preference for the IPv4 stack using the following command. > ```sh > java -Djava.net.preferIPv4Stack=true -jar lra-coordinator-swarm.jar > ``` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2685. ---------------------------------- > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Critical > Fix For: 5.9.1.Final > > > **(some commits that reference this issue are actually for https://issues.jboss.org/browse/JBTM-2955)** > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2685: ----------------------------------- Fix Version/s: 5.9.1.Final > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Critical > Fix For: 5.9.1.Final > > > **(some commits that reference this issue are actually for https://issues.jboss.org/browse/JBTM-2955)** > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2942?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2942. ---------------------------------- > LRA tests failed when building with the JDK9 > -------------------------------------------- > > Key: JBTM-2942 > URL: https://issues.jboss.org/browse/JBTM-2942 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Amos Feng > Assignee: Michael Musgrove > Priority: Major > Labels: jdk9 > Fix For: 5.9.1.Final > > > The lra-test still failed with java.lang.IllegalArgumentException when deploying the war. It looks like the wildfly-swarm does support the JDK9 currently. Also I find 1 and 2 with the same issues. > 1. https://stackoverflow.com/questions/46449735/wildfly-swarm-deployment-cra... > 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-whi... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2942?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2942: ----------------------------------- Fix Version/s: 5.9.1.Final > LRA tests failed when building with the JDK9 > -------------------------------------------- > > Key: JBTM-2942 > URL: https://issues.jboss.org/browse/JBTM-2942 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Amos Feng > Assignee: Michael Musgrove > Priority: Major > Labels: jdk9 > Fix For: 5.9.1.Final > > > The lra-test still failed with java.lang.IllegalArgumentException when deploying the war. It looks like the wildfly-swarm does support the JDK9 currently. Also I find 1 and 2 with the same issues. > 1. https://stackoverflow.com/questions/46449735/wildfly-swarm-deployment-cra... > 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-whi... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2920) Investigate the use of transactions within a reactive microservices environment

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2920?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2920. ---------------------------------- > Investigate the use of transactions within a reactive microservices environment > ------------------------------------------------------------------------------- > > Key: JBTM-2920 > URL: https://issues.jboss.org/browse/JBTM-2920 > Project: JBoss Transaction Manager > Issue Type: Task > Environment: * > Reporter: Ondrej Chaloupka > Assignee: Martin Stefanko > Priority: Major > Labels: student > > Investigate the use of a transaction manager when used within a reactive microservices environment[1][2]. > h2. Motivation > Reactive microservice architecture is a trending architectural pattern. The reactive architecture could simply be defined as a system where messages are sent to a jms queue or a specialized event storage and other services are registered to, for being notified when an event is generated to be able to react on it. Synchronous calls from a service to a service are not meant to be a good practice in such system. Here all the communication between services is done with message passing through the event storage. > Such a system is expected to decouple data [3] where each microservice manages data, which needs for working, on its own. Still there are cases where some data coordination is needed. As the all communication is asynchronous it may be that we need to modify the transaction manager away from synchronous operations. One possibly good match seems to be the Saga transactions[4] and eventual consistency[5][6] but handling of them is fitting to the message driven system. The way of understanding Saga in microservice world could be overviewed at [15]. > Narayana transaction manager is good in managing Saga transactions where having long history experience from running it for WS[7] or managing consistency in NoSQL databases[8]. But Narayana is designed to manage transactions in synchronous way. The transaction context is normally passed along a RPC call where the transaction is finished after such synchronous call is returned back to the caller. > h2. Steps to go > The point here is to investigate on the topic of usage Saga in reactive architecture, gather working solutions - especially in Java world (some references eg. [9][10][11][12][13][14]), get experience in how they are working and on top of this experience considering implementation of the reactive approach with Narayana. It may be that Narayana requires some modification to execute optimally for such task and then it’s up to reconsideration if some greenfield implementation should be started. As the last step there should be created some sample project (ie. quickstart) where the usage of the implementation would be shown. > With that we expect usage of projects in Red Hat portfolio. The sample project would be probably implemented with usage of the Vert.x, meybe there could be considered usage of Infinispan or AMQ7 for handling events. > h2. Expected output > The expected output of this effort is > * A research document with state of the art. > ** Overview of what are the problem of the synchronous/blocking approach. > ** What are the other approaches that people have to this problem, > * A proof-of-concept implementation > ** Preferably with use of Narayana transaction manager prepare a service capable to manage transactions in world of reactive microservices > * An example/quickstart showing this in practical terms > ** A proof that a transaction manager can be made to work in an asynchronous environment. For example if you have a Vert.x event and it has to commit a transaction. The handler for that message currently does sync ops with transaction manager and that blocks. One of the goals for the project is to prevent blocking of threads in an async environment. > h2. Resources > [1] [https://www.youtube.com/watch?v=STKCRSUsyP0|https://www.youtube.com/watch... 2017, The Many Meanings of Event-Driven Architecture, Martin Fowler) > [2] [http://www.oreilly.com/programming/free/reactive-microservices-architectu...] (Reactive Microservices Architecture) > [3] [http://blog.christianposta.com/microservices/the-hardest-part-about-micro...] (The Hardest Part About Microservices: Your Data) > [4] [https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf] (Sagas paper) > [5] [http://queue.acm.org/detail.cfm?id=2462076] (Eventual Consistency Today: Limitations, Extensions, and Beyond) > [6] [http://queue.acm.org/detail.cfm?id=3025012] (Life Beyond Distributed Transactions) > [7] [http://narayana.io//docs/project/index.html#d0e14874] (Narayana doc, WS-Business Activity) > [8] [http://jbossts.blogspot.cz/2014/05/bringing-transactional-guarantees-to.html] (Bringing Transactional Guarantees to MongoDB) > [9] [https://www.youtube.com/watch?v=0UTOLRTwOX0] (Distributed Sagas: A Protocol for Coordinating Microservices - Caitie McCaffrey - JOTB17) > [10] [https://www.youtube.com/watch?v=YPbGW3Fnmbc] (Using sagas to maintain data consistency in a microservice architecture by Chris Richardson) > [11] [http://www.axonframework.org] > [12] [http://eventuate.io] > [13] [https://docs.particular.net/nservicebus/sagas] (.NET NServiceBus Saga) > [14] [https://www.youtube.com/watch?v=Rm8n-H6zI1k] (Dr. Roland Kuhn: Reactive Design Patterns, Akka) > [15] [http://microservices.io/patterns/data/saga.html] (Pattern: Saga) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3085) Compensations test fail because of WildFly module changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3085?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3085. ---------------------------------- > Compensations test fail because of WildFly module changes > --------------------------------------------------------- > > Key: JBTM-3085 > URL: https://issues.jboss.org/browse/JBTM-3085 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Affects Versions: 5.9.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.9.2.Final > > > There was change in module dependencies for compensations (see at https://issues.jboss.org/browse/WFLY-11421) which requires changes into testsuite of compensations. > Currently the narayana CI XTS tests are failing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3085) Compensations test fail because of WildFly module changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3085?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3085: ----------------------------------- Fix Version/s: 5.9.2.Final > Compensations test fail because of WildFly module changes > --------------------------------------------------------- > > Key: JBTM-3085 > URL: https://issues.jboss.org/browse/JBTM-3085 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Affects Versions: 5.9.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.9.2.Final > > > There was change in module dependencies for compensations (see at https://issues.jboss.org/browse/WFLY-11421) which requires changes into testsuite of compensations. > Currently the narayana CI XTS tests are failing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3040) Include more logging in LRA state changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3040?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3040. ---------------------------------- > Include more logging in LRA state changes > ----------------------------------------- > > Key: JBTM-3040 > URL: https://issues.jboss.org/browse/JBTM-3040 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > > We have a test that fails fairly regulary due to timeout: > Tests run: 26, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 98.564 sec <<< FAILURE! - in io.narayana.lra.participant.SpecIT > timeLimitRequiredLRA(io.narayana.lra.participant.SpecIT) Time elapsed: 0.868 sec <<< FAILURE! > java.lang.AssertionError: timeLimitRequiredLRA: compensate should have been called expected:<1> but was:<0> > at io.narayana.lra.participant.SpecIT.timeLimitRequiredLRA(SpecIT.java:608) > Results : > Failed tests: > SpecIT.timeLimitRequiredLRA:608 timeLimitRequiredLRA: compensate should have been called expected:<1> but was:<0> -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2019