"OrionRemoteException: Disconnected: Connection timed out"- slowness

Question

Hi all,
I have a bit of a head scratcher of a problem here.
I have an StatelessSessionBean deployed on an Oracle 9.0.4.0.0 server, which I connect to from 3 different J2EE clients All three of the clients intermittantly get "OrionRemoteException: Disconnected: Connection timed out" messages when invoking the create() method on the EJB Home.
While I'd like to get to the bottom of the Disconnect, I'm not too worried about that right now.
The real issue is that on one of the clients, I dont get the timeout returned for 10 (TEN) minutes. Once I get the timeout, the application resets the home instance, and everything recovers sub second.
Interestingly, the EJB is called from both inside the Container, and from a standalone (non-J2EE) application. Both get the slow timeout.
The slow client is
OS     AIX 4.3
JDK     IBM JDK 1.3.1
AppServer     IBM Websphere 5.0.0
J2EE     1.3
The fast(er) client where the disconnect message comes back in about a minute is
OS     SunOS 5.8
JDK     Sun JDK 1.4.2_05-b04
AppServer     BEA Weblogic 8.1.4
J2EE     1.3
Oracle Server
OS     SunOS 5.8
JDK     Sun JDK 1.4.1_03
AppServer     Oracle App Server 10g (9.0.4)
J2EE     1.3
So the issue is when I invoke
remote = (MyService) PortableRemoteObject.narrow(home.create(), MyService.class);
it intermittantly (<1%) takes 10 minutes before the home.create() method returns the exception "OrionRemoteException: Disconnected: Connection timed out"
For the record, the home object may have been created some time previously as it is cached.
So the questions
Is there any way to set a client timeout?
Why is the timeout behaviour different for the different clients?
Last but not least
Any suggestions for why I'm getting disconnected also appreciated, although I suspect this may be to do with my network environment :-)
For background.....
When creating the Home object, the Initial Context is setup using these config settings
provider.url=ormi://x.x.x.x/MyService
factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
jndi.name=MyServiceEJB
env.put(Context.PROVIDER_URL, providerUrl);
env.put(Context.INITIAL_CONTEXT_FACTORY, initialFactory);
env.put(Context.SECURITY_PRINCIPAL, principal);
env.put(Context.SECURITY_CREDENTIALS, credentials);
InitialContext ic = null;
try {
ic = new InitialContext(env);
} catch (NamingException ne) {
log.error("Unable to lookup new InitialContext");
//rethrow exception
throw ne;
Then the home object is retrieved.
home = (PortServiceHome) PortableRemoteObject.narrow(
ic.lookup(jndiName),
PortServiceHome.class);

Answer 1

Hi Chris,
Have u found any work around / Solution for the problem. If yes pls share with us. We are having similar problem. We have deployed Stateless session beans in 9.0.2.3 cotainers. From client we are getting "A remote host did not respond within the timeout period" exception. But in the server we found
java.io.EOFException
     at com.evermind.server.rmi.RMIConnection.readCommand(RMIConnection.java(Compiled Code))
     at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:460)
     at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:276)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:802)
     at java.lang.Thread.run(Thread.java:513)
RMIConnection Disconnected
The client program is a multithreaded program which will route the request to multiple application server instances. Because of which we need to restart the Client program to make the application work.
Any help will be highly appreciated.
Thanks
Suresh.M