How to prevent RMI calls inside same VM with EJB Session ?

[tbo]

Hello,

Wtih JBOSS 3.2.3, we observe using Borland Optimize It! Server Trace that some RMI calls (around 20% of transaction time) are used when trying to get EJB session (stateless) from JSP calls. The application is all deployed in an EAR in the same VM.

In forums and docs, it seems that JBOSS may use optimized local call by reference when objects are in the same container.

Using BEA Weblogic or Borland Enterprise Server (BES), with the same application, no RMI calls are made.

We tried out to search around invoker and proxies but no parameters in config files may help them.

Have some one any idea to prevent RMI calls inside the container and gain in performance in response time.

Thanks.

[starksm64]

The only rmi call this could be is the JNDI naming service. This would indicate that you are not using the no arg ctor of the InitialContext and are supplying a provider url which triggers the rmi call. If its not the naming service, show the trace for the call.

[tbo]

Thank you M.Stark for your support,

We thought about this idea and in that case we had removed the line "java.naming.provider.url=jnp://<@IP>:1101" from the jndi.properties file.

It seems in reading your post that it could be a bad factory used in the jndi.properties file. It contains now only 2 lines :
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

I do not understand your expression :"no arg ctor", is there a mistake character ?

In docs, it seems that this factory is default factory, so it does not seems to be the default... Any idea to help us ?

We go on investiguate in that way...

Thank you.

[tbo]

To complete our recent answer, first, we do not specify any url provider in the jndi.properties (as explained upper) so it may be auto-generated by the container.

Then, in our source code, we call the constructor InitalContext with no arguments :

initialContext = new InitialContext();

Then for remote object (all EJB sessions objects) :

Object obj = initialContext.lookup(ejbReferenceComponent);
Object home = PortableRemoteObject.narrow(obj, homeClass);

<String ejbReferenceComponent> is a parameter to identify EJBs.
<Class homeClass> is a parameter to identify waiting class.

Is it possible that the JBOSS implementation (transparent for them) can make a lookup using RMI access instead of local stub access ?

Thank you for your support.

[darranl]

'no arg ctor' = No argument constructor

[starksm64]

The show a stack trace for one of the rmi calls in the optimize it output. You have to explicitly enable call by value semantics through a jboss.xml configuration (or standardjboss.xml) setting.

[tbo]

Thank you darranl, we supposed indeed that this was the translation, as indiquated in our third post...

[tbo]

Thank you M. Stark for your support.

I haven't found any tags in jboss.xml or standardjboss.xml to force jboss to do a call by reference or by value. How can I achieve that ?

[istij]

By using local interfaces instead of remote interfaces you can prevent RMI calls (with local interfaces you will have direct method invocation -- using pass by reference), but you can use both (local and remote) interfaces also. For further inf. please check:

http://www.onjava.com/pub/a/onjava/2001/05/10/ejb.html
http://www.ftponline.com/javapro/2002_08/online/j2ee_rdahbura_08_14_02/
http://www.devx.com/getHelpOn/10MinuteSolution/16677/1954?pf=true