10:40 a.m.
[
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)