[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:
----------------------------------
This is a duplicate of a GitHub issue I opened [here][https://github.com/jboss-dockerfiles/narayana/issues/7]. It seems perhaps issues are not tracked there. Maybe consider turning them off in the GitHub preferences and adding a link to the Jira here?
> 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
[JBoss JIRA] (JBTM-3118) Protocol family unavailable error in lra-coordinator Docker container
by Lance Ball (Jira)
Lance Ball created JBTM-3118:
--------------------------------
Summary: 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
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
[JBoss JIRA] (JBTM-3104) Define a separate CI profile for LRA
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3104?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Ondra Chaloupka created pull request #1420 in GitHub
----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Define a separate CI profile for LRA
> ------------------------------------
>
> Key: JBTM-3104
> URL: https://issues.jboss.org/browse/JBTM-3104
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Build System, LRA
> Reporter: Tom Jenkinson
> Assignee: Ondra Chaloupka
> Priority: Major
>
> This could be similar to how the XTS and RTS profile is constructed.
> Changes are anticipated in the narayana.sh, maybe pom IDK, and the pull job and main job
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (JBTM-3106) Firing an @Initialized(TransactionScoped.class) event
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/JBTM-3106?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Ondra Chaloupka created pull request #80 in GitHub
--------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Firing an @Initialized(TransactionScoped.class) event
> -----------------------------------------------------
>
> Key: JBTM-3106
> URL: https://issues.jboss.org/browse/JBTM-3106
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: JTA
> Affects Versions: 5.9.2.Final
> Reporter: Ondra Chaloupka
> Assignee: Laird Nelson
> Priority: Major
>
> It would be beneficial to have the CDI-specific wrapper around Narayana's TransactionManagerImple that fires an @Initialized(TransactionScoped.class)-qualified event.
> For the CDI, it's a good practice. The all built-in scopes have to provide this behaviour.
>
> The CDI specification says (in section 6.7):
> {quote}
> Portable extensions are encouraged to synchronously fire:
> * an event with qualifier @Initialized(X.class) when a custom context is initialized, i.e. ready for use,
> * an event with qualifier @BeforeDestroyed(X.class) when a custom context is about to be destroyed, i.e. before the actual destruction,
> * an event with qualifier @Destroyed(X.class) when a custom context is destroyed, i.e. after the actual destruction,
> where X is the scope type associated with the context.
> A suitable event payload should be chosen.
> {quote}
>
> The {{begin()}} method a Narayana-supplied but CDI-specific transaction manager wrapping Narayana's "ordinary" one should do:
> {code}
> @Inject
> @Initialized(TransactionScoped.class)
> private Event<Transaction> initializationBroadcaster;
> @Inject @BeforeDestroyed(TransactionScoped.class)
> private Event<Transaction> beforeDestructionBroadcaster;
> @Inject @Destroyed(TransactionScoped.class)
> private Event<TransactionManager> destructionBroadcaster;
> // in its begin() method:
> super.begin();
> initializationBroadcaster.fire(this.getTransaction());
> // in its commit() and rollback() methods and anywhere else I'm forgetting:
> beforeDestructionBroadcaster.fire(this.getTransaction());
> super.commit(); // or rollback or whatever
> destructionBroadcaster.fire(this);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (JBTM-3117) Upgrade to the latest LRA spec version
by Anonymous (Jira)
[ https://issues.jboss.org/browse/JBTM-3117?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Martin Stefanko created pull request #1419 in GitHub
----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> 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
[JBoss JIRA] (JBTM-3117) Upgrade to the latest LRA spec version
by Martin Stefanko (Jira)
Martin Stefanko created JBTM-3117:
-------------------------------------
Summary: 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
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