When a client from 7.1.0.CR1 attempts to connect to EAP 7.0, it logs an IllegalArgumentException and then hangs.
09:44:31,396 INFO [org.jboss.ejb.client.EJBClient:53] JBoss EJB Client version 4.0.0.Final-redhat-1 Exception in thread "XNIO-1 task-10" java.lang.IllegalArgumentException: Parameter 'nodeName' may not be null at org.wildfly.common.Assert.checkNotNullParamChecked(Assert.java:70) at org.wildfly.common.Assert.checkNotNullParam(Assert.java:48) at org.jboss.ejb.client.NodeAffinity.<init>(NodeAffinity.java:43) at org.jboss.ejb.protocol.remote.ProtocolV1ObjectResolver.<init>(ProtocolV1ObjectResolver.java:43) at org.jboss.ejb.protocol.remote.EJBClientChannel.<init>(EJBClientChannel.java:134) at org.jboss.ejb.protocol.remote.EJBClientChannel$1.handleMessage(EJBClientChannel.java:647) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$receiveMessage$2(RemoteConnectionChannel.java:361) 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)
This issue is new in CR1. I suspect it was caused by this commit https://github.com/wildfly/jboss-ejb-client/commit/932357490b01534ff2880e312f39632ea89c53ce which implements a fix for JBEAP-12445.
- is caused by
-
JBEAP-12445 EJB client from EAP 7.0 is sometimes authenticated as $local even when it is forbidden
-
- Closed
-
- is incorporated by
-
JBEAP-12888 Upgrade JBoss EJB Client to 4.0.1.Final
-
- Closed
-
