Issue

• If a non-clustered EJB application is deployed, and a client tries to access it, by defining only one server connection, the expectation is that exact this server is used and, if this server fails, the EJB can no longer be invoked.

  • It seems if there is a clustered application deployed at the same time, the non clustered application changes its behaviour to somewhat clustered, with LB and failover.
  • The same problem is visible if there is a mix of clustered and non clustered EJB's in one application archive

• If bean is not annotated with @clustered, load-balancing happens only among the servers available at the time the client initially connects, and no load-balancing happens to servers re-started after an outage.
  However, if one single @clustered annotated EJB is deployed on the server, in any application, then the @clustered annotation seems to be applicable to all other EJB on that server.
  This behaviour looks rather awkward and seems to be linked to the "cluster component" of the server being initialized only when the first @clustered annotated EJB is deployed.