JBoss 7.1.1.-Final server-to-server remoting working a little too well?

[tinche]

Hi,

as the title says, I'm using JBoss remoting as described here: https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance (two JBoss 7.1.1.-Final instances).

This works OK when I get the remote bean over the ejb: namespace explicitly (well, it doesn't reconnect, and has problems propagating exceptions, but whatever).

I also have two identical applications (with EJBs, obviously) deployed in both JBoss instances. The problem is that a different EJB on JBoss-1 sometimes calls the application on JBoss-2 through the java: namespace.

I use a @Produces producer field in a dummy resources class, with an @EJB invocation, and an @Inject annotation on my EJB. This is what I'm looking up:

{code}@EJB(lookup="java:global/localconf/localconf/LocalConfiguration!xxx.LocalConfiguration"){code}

So why is this sometimes going over the wire? And how do I stop it? I was under the impression the ejb: scheme should be explicitly used to do remote calls.

Thanks in advance.

[jaikiran]

Within the server, the java:global, java:app, java:comp JNDI names pointing to remote EJB interfaces are all backed by the EJB client API - which means it behaves the same as it would when you use ejb:. Although for target EJBs that reside on the same server instance, the implementation ensures that the unnecessary remoting overhead isn't applied. You shouldn't be seeing any network calls. I think 7.1.1.Final should behave the same but it's better to try a latest released version http://www.jboss.org/jbossas/downloads.html

[tinche]

Thanks for the reply, I'll try the EAP alpha and get back to you.