Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3118

Protocol family unavailable error in lra-coordinator Docker container

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 5.9.5.Final
    • 5.9.3.Final
    • LRA
    • None

      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
      ```

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              lball1@redhat.com Lance Ball
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: