EJB Lookup Frustration

Question

Hello,
We have 2 OC4J instances deployed in our application. Both the OC4J instances run on seperate machines on seperate Oracle J2EE (Standalone) installations. One of the OC4J instances has an EJB application which we try to call from the other OC4J instance. We use normal Java Context lookups with the following code:
env                     =      new Hashtable();
               //env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
               env.put(Context.INITIAL_CONTEXT_FACTORY,InitialDataLoader.getPropertyValue("INITIAL_CONTEXT_FACTORY"));
               env.put(Context.SECURITY_PRINCIPAL, "admin");
               env.put(Context.SECURITY_CREDENTIALS, "welcome");
               //env.put(Context.PROVIDER_URL, "ormi://localhost:3108/fcxmlg38");
               env.put(Context.PROVIDER_URL,InitialDataLoader.getPropertyValue("PROVIDER_URL"));
               env.put("dedicated.connection","true");
               System.out.println("environment connection is*********"+env);
               Log.warn("hashtable of the context is****"+env,"UtilityWarn.log");
               ctx                     =      new InitialContext(env);
Object obj = ctx.lookup(strFlexmlJndiName);
Log.warn("This Object is*****"+obj,"UtilityWarn.log");
aIFEjbProcHome = (IFEjbProcHom)PortableRemoteObject.narrow(obj,IFEjbProcHom.class);
aIFEjbProcRem = aIFEjbProcHome.create();
The point is we get the handle to the remote...but after a period of inactivity when the application tries to access the EJB , the application hangs....on start and stop of the OC4J instances, we get the handle again...This is turning out to be frustrating as there seems to be no logic to this kind of "un"persistent connection...any kind of help would be gladly appreciated...thanks.....
a very frustrated developer....VJ

Answer 1

Hello,
The version of the Oracle Application Server is:
9.0.2.0.0. So using "opmn:ormi" is out of the question
The problem seems to crop up pretty often. "dedicated.rmicontext=true" is for version 9.0.3 and above not for Base Release. We have exhausted all options of maintaining a dedicated connection...because it behaves very wierdly....A new problem is that the first hit after an inactivity results in a hang ...but subsequent hits give us a proper response from the EJB....This is really getting frustrating as I am just not able to predict the reason for this uncertainty....
Can someone please enlighten me as I have started going back to my basics in EJB to actaully understand how this stuff works...
Thanks....Still very frustrated to the core....
VJ