8 Replies Latest reply on Dec 23, 2017 10:59 PM by lingguang

Cluster EJB problem with "-b 0.0.0.0"

lingguang Dec 20, 2017 5:07 AM

I have two Wildfly 9.0 nodes, which start with --server-config=standalone-full-ha.xml -b 0.0.0.0

And a clustered stateless session bean are deployed to these nodes.

A standalone client uses following properties to make the ejb call. Only the info of the first node has been provided.

{

org.jboss.ejb.client.scoped.context=true

java.naming.factory.url.pkgs=org.jboss.ejb.client.naming

invocation.timeout=300000

remote.connections=10_101_7_124_8080

remote.connections.connect.eager=false

remote.connection.10_101_7_124_8080.host=10.101.7.124

remote.connection.10_101_7_124_8080.port=8080

remote.connection.10_101_7_124_8080.username=testuser

remote.connection.10_101_7_124_8080.password=testpwd

remote.connection.10_101_7_124_8080.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.10_101_7_124_8080.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS=JBOSS-LOCAL-USER

remote.connection.10_101_7_124_8080.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false

remote.clusters=ejb

remote.cluster.ejb.username=testuser

remote.cluster.ejb.password=testpwd

remote.cluster.ejb.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS=JBOSS-LOCAL-USER

remote.cluster.ejb.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false

}

The problem is that it fails to call the second node, because it tries to connect to 0.0.0.0.

Dec 20, 2017 12:49:20 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver

INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='ds1', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='0.0.0.0', destinationPort=8080}], resolvedDestination=[Destination address=0.0.0.0, destination port=8080]} in cluster ejb

java.lang.RuntimeException: java.net.ConnectException: Connection refused: no further information

at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92)

at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:80)

at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)

at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)

at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:469)

at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:443)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: java.net.ConnectException: Connection refused: no further information

at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)

at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)

at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)

at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)

at ...asynchronous invocation...(Unknown Source)

at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)

at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)

at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)

at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)

at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:78)

... 8 more

I'm doing a product migration from Jboss4.2 to Wildfly 9, seems the clustered ejb works with -b 0.0.0.0 in 4.2.

Does anyone know if these is a behavior change or I have missed some configuration? Thanks!

1. Re: Cluster EJB problem with "-b 0.0.0.0"

rhusar Dec 20, 2017 5:12 AM (in response to lingguang)

If you inspect the WildFly configuration you will stumble upon interfaces section which formalized interfaces for public (e.g. HTTP services), management and private (e.g. cluster communication). Configured those properly. Binding to any-address in an antipattern.

Nevertheless, 0.0.0.0 being sent to the EJB client is a bug.
Actions
2. Re: Cluster EJB problem with "-b 0.0.0.0"

rhn-support-abhati Dec 20, 2017 8:02 PM (in response to lingguang)

Try to use specific IP's instead of 0.0.0.0 to form a cluster.
You can create a UDP or a TCP based cluster as well.
Actions
3. Re: Cluster EJB problem with "-b 0.0.0.0"

jaikiran Dec 20, 2017 11:13 PM (in response to lingguang)

This does look like a bug. However, WildFly 9.x is way too old and there are no more 9.x releases. Is this something that you can reproduce against latest released WildFly 11.0.0.Final?
Actions
4. Re: Cluster EJB problem with "-b 0.0.0.0"

lingguang Dec 21, 2017 1:51 AM (in response to rhusar)

Thanks Radoslav.
We are currently using http-remoting-connector for both remoting and HTTP service, maybe we need use separate connectors for workaround.
Actions
5. Re: Cluster EJB problem with "-b 0.0.0.0"

lingguang Dec 22, 2017 12:26 AM (in response to jaikiran)

Yes, I can reproduce this issue on WildFly 11.0.0.Final. The ejb cluster still does not work when bind to 0.0.0.0.
After change to bind IP address, it works. But we can get a NPE when first call failed and the next calls were OK.

called
called
failed:
java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202)
at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:393)
at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115)
at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450)
at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
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)
called
called
Actions
6. Re: Cluster EJB problem with "-b 0.0.0.0"

lingguang Dec 22, 2017 4:42 AM (in response to lingguang)

Thanks all. Seems adding the client-mapping solved my problem and the cluster ejb now works as expected along with -b 0.0.0.0.

<socket-binding name="http" port="${jboss.http.port:8080}">
<client-mapping destination-address="${jboss.host.name}"/>
</socket-binding>
Actions
7. Re: Cluster EJB problem with "-b 0.0.0.0"

jaikiran Dec 22, 2017 5:48 AM (in response to lingguang)

Could you please file a JIRA for this here - JBoss Issue Tracker and point to this thread?
Actions
8. Re: Cluster EJB problem with "-b 0.0.0.0"

lingguang Dec 23, 2017 10:59 PM (in response to jaikiran)

Created.
[WFLY-9641] Cluster EJB can not work with "-b 0.0.0.0" - JBoss Issue Tracker
https://issues.jboss.org/browse/WFLY-9641
Actions

Go to original post