I'm hitting strange behavior when more remote connections defined. I'm running on WildFly 9.0.0-SNAPSHOT and module.xml shows version 2.0.2.Final.

When more than one connection is defined then time to time client fails the connection with IllegalStateException (EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:crashrecovery-jms, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@6aa8217b)

I have defined three remote connections in jboss-ejb-client.properties where 3 of the connections are unavailable (there is no server started). Only one is active where server listens. I've checked it and the server is really running and listening at time when client fails.

I tried to do a bit investigation in code but I have just few observations nothing in details.
The log shows message "Unsupported message received with header 0xffffffff" but it seems that it has nothing to do with the connection problem. This message is shown in the log when connection succeed as well.
It seems that it happens when active connection is taken as a last one in the processing in EjbClientContext#attemptReconnections
https://github.com/jbossas/jboss-ejb-client/blob/2.0/src/main/java/org/jboss/ejb/client/EJBClientContext.java#L1126
Otherwise the client successes with the communication.

I'm attaching test.log and server.log files. At the end of the files it could be seen how the communication was going. The test.log file shows the state when communication succeeded for class CrashHelperTestXAResource (l.128) and at the end when it failed (l.358).

I run the same scenario on EAP6.x and it works fine.