The Wildfly client libraries are used by remote clients to access EJB, Naming and Transaction services on a Wildfly server instance. Two transports are available: a JBoss Remoting transport (EJB/Remoting) and a a pure HTTP transport (EJB/HTTP).

A key difference when using these transports to access a Wildfly cluster is that in the EJB/Remoting case, it is the client itself which manages failover and load balancing through direct access to the nodes in the cluster. In the EJB/HTTP case, failover and load balancing is managed by a load balancer inserted between the client and the cluster.

At present there is no test coverage in the Wildfly clustering testsuite to test failover of EJB client operations when using EJB/HTTP. This issue takes the two key EJB/Remoting failover tests RemoteStatelessEJBFailoverTestCase and RemoteStatefulEJBFailoverTestCase and adapts them to the case of EJB/HTTP.