PQ61462: AFTER PQ61986 (PTF 3) ASSOCIATES A NAMING ISSUE AFTER INSTALL. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer applies ptf 3 and tries to change bootstrap port to something other than 900. This causes a failure when trying to get to the name server. Additional symptoms: NMSV0602E: Name Service unavailableLocal fix Problem summary **************************************************************** * USERS AFFECTED: 1> WebSphere Application Release 4 * * users who have applied the fixpack 3 * * and need to run the adminServer on a * * non-default bootstrap port. * * * * 2> WebSphere Application Release 4 * * users who have applied the fixpack 3 * * and pass the Java ORB properties * * "com.ibm.CORBA.BootstrapPort" and * * "com.ibm.CORBA.BootstrapHost" as the env * * parameter of new InitialContext(env) in * * order to use a different host or port, * * other than the default host and port. * **************************************************************** * PROBLEM DESCRIPTION: After fixpack 3 and starting the * * AdminServer with a non default port, * * the nanny service won't come up and * * the nanny trace shows * * org.omg.CORBA.COMM_FAILURE exceptions * * and warning message NMSV0602E: Naming * * Service unavailable even after the * * AdminServer comes up. * * * * 2> If customers who have applied ptf3 * * and set the Java ORB properties * * com.ibm.CORBA.BootstrapPort and/or * * com.ibm.CORBA.BootstrapHost to a non * * default port number and/or host and * * use those properties as the env * * parameter passed in the new * * InitialContext(env) call, the * * customer's those setting will be * * ignored and the default port number * * and/or host will be used. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the AdminServer is started with a non default port number, the nanny service won't start and the nanny trace shows the warning message NMSV0602E: Naming Service unavailable with org.omg.CORBA.COMM_FAILURE exception even after the AdminServer comes up. The root cause of this failure is that the Java ORB properties com.ibm.CORBA.BootstrapHost and com.ibm.CORBA.BootstrapPort were ignored if they were passed in as the parameter "env" of new InitialContext(env) call due to a naming defect. This problem was introduced by the fixpack 3 of WebSphere Application Server release 4Problem conclusion If the Java ORB properties com.ibm.CORBA.BootstrapHost and com.ibm.CORBA.BootstrapPort are passed as the parameter "env" of new InitialContext(env) call, the host and/or port number are/is being ignored, instead, the default host and/or port number are/is used. That results in a problem with the nanny service failing to start with warning message NMSV0602E: Naming Service unavailable and org.omg.CORBA.COMM_FAILURE exception when AdminServer starts with the non-default bootstrap port after the fixpack 3 being applied to WebSphere Application Server release 4. This was caused by a naming defect, which was fixed via this APAR with the efix PQ61462.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ61462
IBM Group: Software Group
Modified date: Jun 6, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.