PQ87768: A ORG.OMG.CORBA.NO_IMPLEMENT EXCEPTION IS THROWN DURING AN EJB LOOKUP TO A CLUSTER THAT HAS RUNNING CLUSTER MEMBERS

 A fix is available

PQ87768; 5.0.2.3: org.omg.CORBA.NO_IMPLEMENT exception thrown during EJB lookup



APAR status
Closed as program error.

Error description
This Problem only occurs if PME is installed on top of base/ND.
A org.omg.CORBA.NO_IMPLEMENT exception is thrown during an EJB
lookup. The problem occurs at random in a system that
may have been running fine. To resolve the problem, the cluster,
where the client is attempting to lookup the EJB, has to be
restarted.
An example of the stacktrace the client received may look like
the following:

org.omg.CORBA.NO_IMPLEMENT: No Useable Targets minor code:
49421040 completed: No
at
com.ibm.ws.cluster.router.selection.WLMLSDRouter.getNextTarget(U
nknown Source)(Compiled Code)
at
com.ibm.ws.cluster.router.selection.WLMClientForCommonRouterImpl
.getNextTarget(Unknown Source)(Compiled Code)
at
com.ibm.ws.wlm.client.WLMClient.getNextTarget(WLMClient.java(Com
piled Code))
at
com.ibm.ws.orbimpl.services.lsd.LocationServiceDaemon.getDirectI
OR(Unknown Source)(Compiled Code)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java(Compiled
Code))
at
com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java(Inlined
Compiled Code))
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java(Compiled
Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)"
Local fix
Recycle the cluster of the ejb.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server PME Edition     *
*                 users of Clustering, or Workload             *
*                 Management (WLM).                            *
****************************************************************
* PROBLEM DESCRIPTION: A org.omg.CORBA.NO_IMPLEMENT            *
*                      exception is thrown during an EJB       *
*                      lookup.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This Problem only occurs if PME is installed on top of base/ND.

A org.omg.CORBA.NO_IMPLEMENT exception is thrown during an EJB
lookup.  The problem occurs at random in a system that
may have been running fine.  To resolve the problem, you must
restart the cluster on which the client is attempting to lookup
the EJB.  An example of the stacktrace the client
received may look like the following;

org.omg.CORBA.NO_IMPLEMENT: No Useable Targets
                            minor code: 49421040  completed: No
at com.ibm.ws.cluster.router.selection.WLMLSDRouter
                  .getNextTarget(Unknown Source)(Compiled Code)
at com.ibm.ws.cluster.router.selection
                                   .WLMClientForCommonRouterImpl
                   .getNextTarget(Unknown Source)(Compiled Code)
at com.ibm.ws.wlm.client.WLMClient
                   .getNextTarget(WLMClient.java(Compiled Code))
Problem conclusion
An incorrect datatype was used.
Temporary fix
Restart the effected cluster.
Comments
APAR information
APAR number PQ87768
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-04-20
Closed date 2004-06-14
Last modified date 2004-06-14

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information
Fixed component name WAS ENTERPRISE
Fixed component ID 5630A3700

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ87768
IBM Group: Software Group
Modified date: Jun 14, 2004