[JBoss JIRA] (JBTM-3125) Some LRA&RTS tests uses wrong String.format paramters
by Ondra Chaloupka (Jira)
Ondra Chaloupka created JBTM-3125:
-------------------------------------
Summary: Some LRA&RTS tests uses wrong String.format paramters
Key: JBTM-3125
URL: https://issues.jboss.org/browse/JBTM-3125
Project: JBoss Transaction Manager
Issue Type: Bug
Components: LRA, REST
Affects Versions: 5.9.3.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
Some tests uses wrong {{String.format}}. For example wrong number of arguments for the {{format}} methdo
{code}
System.out.printf("SRA: %s: Updating hotel participant state to: ", bookingId, status);
{code}
should be
{code}
System.out.printf("SRA: %s: Updating hotel participant state to: %s", bookingId, status);
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Anonymous (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Martin Stefanko created pull request #1426 in GitHub
----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> 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
>
> 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, 8 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Martin Stefanko (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Martin Stefanko reassigned JBTM-3123:
-------------------------------------
Assignee: Martin Stefanko (was: Michael Musgrove)
> 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
>
> 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, 8 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Lance Ball (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Lance Ball updated JBTM-3123:
-----------------------------
Description: 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}}. (was: 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}}, 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}}.)
> 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: Michael Musgrove
> Priority: Minor
>
> 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, 8 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Lance Ball (Jira)
[ https://issues.jboss.org/browse/JBTM-3123?page=com.atlassian.jira.plugin.... ]
Lance Ball updated JBTM-3123:
-----------------------------
Description: 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}}, 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}}. (was: 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}}, 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 {{200}}.)
> 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: Michael Musgrove
> Priority: Minor
>
> 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}}, 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, 8 months
[JBoss JIRA] (JBTM-3123) LRA POST to "start" has Incorrect @ApiResponse annotation
by Lance Ball (Jira)
Lance Ball created JBTM-3123:
--------------------------------
Summary: 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: Michael Musgrove
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}}, 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 {{200}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (JBTM-3118) Protocol family unavailable error in lra-coordinator Docker container
by Lance Ball (Jira)
[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ]
Lance Ball commented on JBTM-3118:
----------------------------------
Just writing to confirm that I pulled the updates locally and everything is working as expected. Thanks again!
> 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: Ondra Chaloupka
> Priority: Major
>
> 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, 8 months
[JBoss JIRA] (JBTM-3118) Protocol family unavailable error in lra-coordinator Docker container
by Lance Ball (Jira)
[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ]
Lance Ball commented on JBTM-3118:
----------------------------------
[~ochaloup] thank you!
> 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: Ondra Chaloupka
> Priority: Major
>
> 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, 8 months
[JBoss JIRA] (JBTM-3118) Protocol family unavailable error in lra-coordinator Docker container
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3118:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
I'm resolving this issue as I did what was discussed here. if you have some troubles with the current state [~lanceball], please feel free to reopen or create a new issue. Thank you!
> 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: Ondra Chaloupka
> Priority: Major
>
> 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, 8 months