|
Problem(Abstract) |
After restarting a WebSphere Application Server node
agent, a web application on an application server in this node could no
longer find an EJB that's on a different application server. The
application worked fine until the node agent restart.
The application on application server 1 could lookup an EJB after
restarting application server 2. The application on application server 2
continued to work and had no problems during and after the node agent
restart. Only the application on application server 1 could no longer find
an EJB on application server 2 after its node agent was restarted.
Example of the exception found in the log files:
[12/11/03 16:29:27:736 EST] 79eb8 Helpers W NMSV0610I: A NamingException
is being thrown from a javax.naming.Context implementation. Details
follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: lookup
Context name: MyNetwork/nodes/mynode/servers/MyServer
Target name: com/ibm/MyEJB
Other data:
Exception stack trace: javax.naming.NamingException: Error during
resolve.
Root exception is org.omg.CORBA.OBJECT_NOT_EXIST:
minor code: 1229126658 completed: No |
|
|
|
Cause |
This is a known problem. Fix PQ83430, to address this
issue. |
|
|
Resolving the
problem |
Apply the WebSphere Application Server cumulative fix 4 or
higher for version 5.0.2 (i.e. 5.0.2.4 or higher) contains PQ83430 which
solves this issue. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Product
Alias/Synonym |
WAS |
|
|
|
|