Skip to Content
0
Former Member
Sep 25, 2005 at 03:35 PM

Remote EJB woes

52 Views

Hi all,

I've developed a simple J2EE application. This application consists of a WebApp and an EJB. The EJB runs on a different server to the WebApp, so I'm using the standard Remote Invication code to connect. I can't paste the code here, and it's on a different machine. Suffice it to say, however, that from reading through the forum, it's no different from any other code that's there.

We have 4 environments here. 2 of then enviroment consists of 2 servers - one is running WebAS 6.40 with EP6, and the other is just running WebAS 6.40. These are Dev and SysTest. The other 2 environment are clustered, with 2 of each of the aforementioned boxes setup in a cluster.

This is all running on Window2003

My application is running on the WebAS + EP6 servers only.

When I run my application on Dev and get it to connect to a server on SysTest, it connects no problem, and everything works as expected.

When I run it on SysTest and get it to connect to one of the UTT servers, it fails.

When I take the code for getting the InitialContext and doing the lookup() and run this in a standalone Java class from the command line, it will connect from the SysTest server to the UTT server with no problems.

I can't see why it should fail when running within the WebAS server, and not fail when running on the same box from the command prompt.

I have tried to connect by giving it and Adminstrator user details, and by not giving it those details. On the cluster, I have tried to connect to the DI and CI instances seperate, and to the virual IP of the cluster. All to no avail.

The errors that I have been receiving are:

- BaseLoginException: Cannot create new RemoteLoginContext instance.

- P4BaseConnectionException: Incorrect client ID. The stub is not connected yet.

among others.

(both of the above are the root cause of a NamingException)

Has anyone any ideas on what I can do to resolve this. I know my application works (as proved from connection from Dev to SysTest), and I know it's not a firewall issue (as proved by running the InitialContext code from the command line).

Thanks,

Gary