-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR12, 7.1.0.DR13, 7.1.0.DR14
-
Regression, Blocks Testing
-
-
-
-
-
-
When creating EJB client context in the new EJB client and setting "remote.connections" property like this:
jndiProperties.put("remote.connections", "perf18, perf19, perf20, perf21");
the EJB client is not able to lookup remote bean and is returning this error:
java.lang.IllegalStateException: EJBCLIENT000024: Not able to find EJB matching "StatelessEJBLocator for "clusterbench-ee7/clusterbench-ee7-ejb/RemoteStatefulSBImpl", view is interface org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB, affinity is None" at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:405) at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:387) at org.jboss.ejb.client.EJBClientContext.createSession(EJBClientContext.java:367) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:270) at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:141) ... 11 more
If I specify only one connection like this:
jndiProperties.put("remote.connections", "perf18");
EJB client successfully connects.
This effectively prevents users from using EJB client with clustering features, unless they apply complicated workarounds (set affinity for EJB proxies and sessions manually using EJB client internal API)
- blocks
-
JBEAP-8635 Recovery doesn't work when transaction is propagated thru EJB remoting
- Closed
- is blocked by
-
JBEAP-9355 EJB cluster proxies are not failing over
- Closed