Calling remote EJB ended up calling the local EJB

[dkoon]

We are migrating an application from Weblogic to JBoss. We have a problem in calling a remote EJB.

The scenario is this: We have two JBoss servers on two machines. The application with EJB's is deployed on both machines. There is one part of the application that no matter which machine it is executed from, it has to call a method on the local EJB, and the same method on the remote EJB. Both EJB's are the same type, they are just deployed on two machines.

The symptom: Instead of both local and remote EJB's each getting called once, the LOCAL EJB got called TWICE! The remote EJB never got called.

Our code:

In the JNDI code, for both local and remote EJB, the following code with url specified is used:

Properties p = new Properties();
p.put(Context.PROVIDER_URL, urlString);
InitialContext objContext = new InitialContext(p);
Context contxt = objContext.getInitialContext();
EJBHome home = (EJBHome)PortableRemoteObject.narrow(contxt.lookup(lookupName), homeClass);

We have also tried the following but the result is the same:

InitialContext objContext = new InitialContext();
Context contxt = objContext.getInitialContext();
contxt.addToEnvionment(Context.PROVIDER_URL, urlString);
EJBHome home = (EJBHome)PortableRemoteObject.narrow(contxt.lookup(lookupName), homeClass);


Runtime debugging statements from InitialContext environment

###Printing InitialContext environment hashtable for local call:
###Map Key: java.naming.provider.url Map value: jnp://192.168.7.91:1099
###Map Key: java.naming.factory.initial Map value: org.jnp.interfaces.NamingContextFactory
###Map Key: java.naming.factory.url.pkgs Map value: org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
###HomeClass : AdminMainAppHome



###Printing InitialContext environment hashtable for remote call:
###Map Key: java.naming.provider.url Map value: jnp://192.168.7.44:1099
###Map Key: java.naming.factory.initial Map value: org.jnp.interfaces.NamingContextFactory
###Map Key: java.naming.factory.url.pkgs Map value: org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
###HomeClass : AdminMainAppHome

As you can see, the InitialContext does have the respective urls, but it is only invoking the local EJB. We know that because we have debugging statements inside the EJB and the local one got called twice.

Request for ideas:

I have searched many of the EJB forum items, and I read Chapter 3 of JBoss 4.01 guide, but still I could not find a solution. JBoss is new to me. Could someone shed some light, as we encountered several issues recently and are now behind schedule? What am I missing? What have we done wrong?

Thanks

[darranl]

There is a problem with calling beans remotely on some versions of JBoss.

http://jira.jboss.com/jira/browse/JBAS-1442

What JBoss version are you using?

Can you try your code on JBoss 4.0.2 RC1 to see if the fix above solves your problem.

[dkoon]

We are using JBoss 4.01 and we are NOT using clustering. This is a case of one JBoss simply talking o another JBoss.

May be I should try this on 4.01 SP1 first, that's the version to plan to go production...

[darranl]

We are using JBoss 4.01 and we are NOT using clustering. This is a case of one JBoss simply talking o another JBoss.

The issue does not describe a clustering issue.

The issue describes how an enhancement made to the clustering code has had an effect on behaviour when calls are made from one server to another.

May be I should try this on 4.01 SP1 first, that's the version to plan to go production...

I doubt it will work, let us know how it goes.

[drakonis]

Same problem, was about to post it. I still actually cannot belive it. Well i use 4.01sp1 so no go with that one. Temporary solution for me is to have them deployed under different names, add a little R for remote to the other one:). It's an overhead, but....

[sksiazek]

This is a problem caused by the clustering code, right ? Can we disable clustering to get around this problem, or is it truly necessary to use a different name in the remote's JNDI ?

[dkoon]

I tried JBoss 4.0.2 RC1 and it DOES work. So can someone tell us when will 4.0.2 become official. We are going production with JBoss in May.