March 2019 - jbossts-issues - Jboss List Archives

[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] when I run {{docker run --rm -p 8080:8080 jbosstm/lra-coordinator}}, the container starts but the lra-coordinator fails to start on this line https://github.com/jboss-dockerfiles/narayana/blob/master/lra/lra-coordin.... To debug what was going on, I used the command {{docker run --rm -it -p 8080:8080 jbosstm/lra-coordinator /bin/bash}} which runs the container, but provides a terminal prompt on the container which allows me to {{cd /deployments}} and run the startup command for the lra-coordinator manually. When I do that, I see the error initially reported. In order to test my work, I start the lra-coordinator by adding the IPv4 flags to the {{java -jar}} command. I think you need to add those flags to the Dockerfile. > 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, 1 month

1
0
0 / 0

[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 commented on JBTM-3118: --------------------------------------- [~goldmann] I would like ask you for guidance in one point. For the Narayana LRA we dockefile we have used base image [`redhat-openjdk-18/openjdk18-openshift`|https://github.com/jboss-dockerfiles/narayana/blob/master/lra/lra-coordinator/Dockerfile]. The WFLY uses the [`jboss/base-jdk`|https://github.com/jboss-dockerfiles/wildfly/blob/master/Dockerfile]. Do I understand correctly that `jboss/base-jdk` should be used in general? [~lanceball] may I check with you why do you the command `docker run --rm -it -p 8080:8080 jbosstm/lra-coordinator /bin/bash` and not something like `docker run --rm -p 8080:8080 jbosstm/lra-coordinator`? Do I understand that was because that way the coordinator was started at all? I would like just understand what is needed to do. Thanks a lot! > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3120) Moving narayana dockerfiles repository to the repository where all jboss dockerfiles reside

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3120?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #3 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Moving narayana dockerfiles repository to the repository where all jboss dockerfiles reside > ------------------------------------------------------------------------------------------- > > Key: JBTM-3120 > URL: https://issues.jboss.org/browse/JBTM-3120 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > > We currently administrate repository https://github.com/jbosstm/jboss-dockerfiles which is out of the date from what is in the jboss generally used https://github.com/jboss-dockerfiles/narayana repository. > We should use the `jboss-dockerfiles/narayana` as it's used by all other projects under JBoss umbrella. > Steps > . retire the https://github.com/jbosstm/jboss-dockerfiles > . move changes done in the `jbosstm/jboss-dockerfiles` to `jboss-dockerfiles/narayana` > . verify if base image used in the LRA coordinator follows those used by other `jboss-dockerfiles` projects -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3121) Create Quarkus LRA extension

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3121: ------------------------------------- Summary: Create Quarkus LRA extension Key: JBTM-3121 URL: https://issues.jboss.org/browse/JBTM-3121 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.9.3.Final Reporter: Martin Stefanko Assignee: Martin Stefanko Quarkus LRA extension would significantly help propagate LRA even before release. It doesn't necessarily needs to be included in the quarkus extension list until we have a stable spec version. -- 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 Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-3118: ------------------------------------- Assignee: Ondra Chaloupka (was: Michael Musgrove) > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3120) Moving narayana dockerfiles repository to the repository where all jboss dockerfiles reside

by Ondra Chaloupka (Jira)

Ondra Chaloupka created JBTM-3120: ------------------------------------- Summary: Moving narayana dockerfiles repository to the repository where all jboss dockerfiles reside Key: JBTM-3120 URL: https://issues.jboss.org/browse/JBTM-3120 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka We currently administrate repository https://github.com/jbosstm/jboss-dockerfiles which is out of the date from what is in the jboss generally used https://github.com/jboss-dockerfiles/narayana repository. We should use the `jboss-dockerfiles/narayana` as it's used by all other projects under JBoss umbrella. Steps . retire the https://github.com/jbosstm/jboss-dockerfiles . move changes done in the `jbosstm/jboss-dockerfiles` to `jboss-dockerfiles/narayana` . verify if base image used in the LRA coordinator follows those used by other `jboss-dockerfiles` projects -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3119) Enhance Narayana README with information about tests

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3119?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3119: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Enhance Narayana README with information about tests > ---------------------------------------------------- > > Key: JBTM-3119 > URL: https://issues.jboss.org/browse/JBTM-3119 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The Narayana `README.md` should contain at least few words about type of tests in the Narayana repository. Any newcomer is confused. See https://github.com/jbosstm/narayana/pull/1403#issuecomment-471367319 -- 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 Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3118?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3118: --------------------------------------- [~tomjenkinson] please, to clarify the https://github.com/jbosstm/jboss-dockerfiles) should be deprecated, we will move changes from `jbosstm/jboss-dockerfiles` to `jboss-dockerfiles/narayana` and our release script should start use the https://github.com/jboss-dockerfiles/narayana, correct? > 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: Michael Musgrove > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3119) Enhance Narayana README with information about tests

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3119?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1421 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Enhance Narayana README with information about tests > ---------------------------------------------------- > > Key: JBTM-3119 > URL: https://issues.jboss.org/browse/JBTM-3119 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The Narayana `README.md` should contain at least few words about type of tests in the Narayana repository. Any newcomer is confused. See https://github.com/jbosstm/narayana/pull/1403#issuecomment-471367319 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3119) Enhance Narayana README with information about tests

by Ondra Chaloupka (Jira)

Ondra Chaloupka created JBTM-3119: ------------------------------------- Summary: Enhance Narayana README with information about tests Key: JBTM-3119 URL: https://issues.jboss.org/browse/JBTM-3119 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Documentation Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka The Narayana `README.md` should contain at least few words about type of tests in the Narayana repository. Any newcomer is confused. See https://github.com/jbosstm/narayana/pull/1403#issuecomment-471367319 -- 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