Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9028

EJB client 4.x can't invoke EJBs if more than one connection in "remote.connections" property is set

XMLWordPrintable

    • 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)

              mvinkler1@redhat.com Michal Vinkler
              mvinkler1@redhat.com Michal Vinkler
              Michal Vinkler Michal Vinkler
              Michal Vinkler Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: