[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: Pull Request Sent (was: Open)
> 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
[JBoss JIRA] (JBTM-3117) Upgrade to the latest LRA spec version
by Michael Musgrove (Jira)
[ https://issues.jboss.org/browse/JBTM-3117?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-3117:
----------------------------------------
The next upgrade is to the following versions:
{quote}
<version.microprofile.lra.api>1.0-20190313.061211-301</version.microprofile.lra.api>
<version.microprofile.lra.tck>1.0-20190313.061212-301</version.microprofile.lra.tck>
{quote}
> Upgrade to the latest LRA spec version
> --------------------------------------
>
> Key: JBTM-3117
> URL: https://issues.jboss.org/browse/JBTM-3117
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: LRA
> Affects Versions: 5.9.3.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Major
>
> Upgrade to the latest LRA API and TCK snapshots:
> ```
> <version.microprofile.lra.api>1.0-20190306.071209-294</version.microprofile.lra.api>
> <version.microprofile.lra.tck>1.0-20190306.071211-294</version.microprofile.lra.tck>
> ```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[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:
---------------------------------------
[~lanceball] thanks. I adjusted your changes and created PR https://github.com/jboss-dockerfiles/narayana/pull/8
> 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
[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:
----------------------------------
Git Pull Request: https://github.com/jboss-dockerfiles/narayana/pull/8
> 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
[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] if it helps at all, [here|https://gist.github.com/lance/47c686634b073d8495e4ad58fe69d261] are the changes I have made locally to test the [work I am doing|https://github.com/lance/crockpot] in Node.js.
> 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
[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][~lanceball] thank you for your remarks. I will fix the lra dockerfile following your suggestions.
> 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
[JBoss JIRA] (JBTM-3122) jbosstm/quickstarts tests can't be run with jdk9+
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3122?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3122:
----------------------------------
Description:
Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the {{arquillian.xml}}.
See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
{code}
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
--add-modules=java.se
{code}
The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.
was:
Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the `arquillian.xml`.
See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
{code}
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
--add-modules=java.se
{code}
The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.
> jbosstm/quickstarts tests can't be run with jdk9+
> -------------------------------------------------
>
> Key: JBTM-3122
> URL: https://issues.jboss.org/browse/JBTM-3122
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.9.3.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Major
>
> Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
> The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the {{arquillian.xml}}.
> See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
> {code}
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
> --add-modules=java.se
> {code}
> The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
> Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBTM-3122) jbosstm/quickstarts tests can't be run with jdk9+
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3122?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated JBTM-3122:
----------------------------------
Summary: jbosstm/quickstarts tests can't be run with jdk9+ (was: jbosstm/quickstars can't be run with jdk9+)
> jbosstm/quickstarts tests can't be run with jdk9+
> -------------------------------------------------
>
> Key: JBTM-3122
> URL: https://issues.jboss.org/browse/JBTM-3122
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.9.3.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Major
>
> Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
> The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the `arquillian.xml`.
> See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
> {code}
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
> --add-modules=java.se
> {code}
> The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
> Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (JBTM-3122) jbosstm/quickstars can't be run with jdk9+
by Ondra Chaloupka (Jira)
Ondra Chaloupka created JBTM-3122:
-------------------------------------
Summary: jbosstm/quickstars can't be run with jdk9+
Key: JBTM-3122
URL: https://issues.jboss.org/browse/JBTM-3122
Project: JBoss Transaction Manager
Issue Type: Bug
Components: Build System
Affects Versions: 5.9.3.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the `arquillian.xml`.
See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
{code}
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
--add-modules=java.se
{code}
The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[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 edited comment on JBTM-3118 at 3/11/19 11:48 AM:
------------------------------------------------------------
[~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.
was (Author: lanceball):
[~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