PK16480: "ORG.OMG.CORBA.NO_IMPLEMENT: NO USEABLE TARGETS" ERROR OCCURS ONJNDI LOOKUP OF EJBS AFTER DEPLOYMENT MANAGER RESTARTS

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
In a clustered topology in WebSphere Application Server V5, when
the deployment manager is restarted, JNDI lookups of EJBs that
are deployed to the cluster may fail with the following error:
.
org.omg.CORBA.NO_IMPLEMENT: No Useable Targets  minor code:
1229066304  completed: No
 at
com.ibm.ws.wlm.client.selection.WLMLSDRouter.getNextTarget(WLMLS
DRouter.java:214)
...
After enough time (could be 30-60 minutes depending on the
number of nodes and cluster members in the topology) passes, the
JNDI lookups will succeed.
.
This occurs because when the deployment manager starts, there is
logic that tries to reconnect to all of the nodes and cluster
members within the cell.  If there are servers in the topology
that are not up, the connection attempt will timeout after three
minutes.  This occurs synchronously on one thread, so if
multiple servers are down, the process can take a long time.
The WLM routing tables are not available during this time, which
causes the EJB requests to fail.
Local fix
The problem can be avoided if all servers in the topology are up
when the deployment manager starts.  If that is not possible,
the amount of time that it takes the deployment manager to
reconnect to the nodes and cluster members can be reduced by
lowering the com.ibm.CORBA.RequestTimeout value.  Its default
value is 180 seconds; try reducing it to 60 seconds for quicker
results.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server version 5.02    *
*                 and 5.1 users with large topologies.         *
****************************************************************
* PROBLEM DESCRIPTION: In a clustered topology in WebSphere    *
*                      Application Server Version5, when the   *
*                      deployment manager is restarted, JNDI   *
*                      lookups of EJBs that are deployed to    *
*                      the cluster may fail with the           *
*                      following error:                        *
*                                                              *
*                                                              *
*                       org.omg.CORBA.NO_IMPLEMENT: No         *
*                      Useable Targets  minor code:            *
*                      1229066304  completed: No               *
*                      at                                      *
*                       com.ibm.ws.wlm.client.selection.       *
*                      WLMLSDRouter.getNextTarget              *
*                      (WLMLSDRouter.java:214)                 *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
*                                                              *
****************************************************************
This occurs because when the deployment manager starts, there is
logic that tries to reconnect to all of the nodes and cluster
members within the cell.  If there are servers in the topology
that are not up (either physical machines, or shut down
WebSphere Application Server instances on a node that is
currently up), the connection attempt may timeout after three
minutes.  This occurs synchronously on one thread, so if
multiple servers are down, the process can take a long time.
The WLM routing tables are not available during this time, which
causes the EJB requests to fail.
Problem conclusion
Logic was added with this APAR to spawn threads to reconnect
the members when the deployment manager starts.

The fix for this APAR is currently targeted for inclusion
in cumulative fixes 5.02.16 and 5.1.1.9.
Please refer to the recommended updates page for delivery
information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
The problem can be avoided if all servers in the topology are up
when the deployment manager starts.  If that is not possible,
the amount of time that it takes the deployment manager to
reconnect to the nodes and cluster members can be reduced by
lowering the com.ibm.CORBA.RequestTimeout value.  Its default
value is 180 seconds; try reducing it to 60 seconds for quicker
results.
Comments
APAR information
APAR number PK16480
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-12-08
Closed date 2006-01-05
Last modified date 2006-08-14

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WLM          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PK16480
IBM Group: Software Group
Modified date: Aug 14, 2006