PQ76596: BBOWADDN FAILS WITH MSG: EXCEPTION IN THREAD " MAIN "

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer attempted to run add a node by running job BBOWADDN
but job fails with msg: Exception in thread "main"
----------------------------------------------------------------
  Proc BBOWADDN kicks off script addNode.sh which sets env vars
and starts a java pgm.  We found that in addNode.sh where the
java invokation is made that CLASSPATH is passed as a parm.
CLASSPATH is not set in either addNode.sh or setupCmdLine.sh
so the USS default profile value for CLASSPATH is used.
  This customer has previous versions of WebSphere on their
system,  so the default profile sets CLASSPATH to contain
those files.  This caused V3 and/or V4 files to be included
when the V5 script addNode.sh invoked java.
------------------------------------------------------------
WORKAROUND: customer removed websphere files from the default
profile var CLASSPATH.  It also appears that one could simply
remove the CLASSPATH variable from the addNode.sh java call
since it does not appear to be used.
ADDITIONAL KEYWORDS: addNode shell script
Local fix
HBC
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Customer attempted to run add a node by *
*                      running job BBOWADDN but job fails with *
*                      msg:                                    *
*                      Exception in thread "main"              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Procedure BBOWADDN kicks off script addNode.sh which sets
environment variables and starts the NodeFederationUtility
program. Presently, CLASSPATH Variable is passed as a parameter
to the jvm. However, CLASSPATH is not set in either addNode.sh
or setupCmdLine.sh so the USS default profile value for
CLASSPATH is used.  The customer has previous versions of
WebSphere on their system,  so the default profile sets
CLASSPATH to contain those files.  This caused WebSphere V3
and/or V4 files to be included when the WebSphere V5 script
addNode.sh invoked the jvm. addNode.sh failed and
NoSuchMethodError exception was thrown. com.ibm.ejs.ras.Tr
:method register(Ljava/lang/Class;Ljava/lang/String;
Ljava/lang/String;)Lcom/ibm/ejs/ras/TraceComponent;
not found.
Problem conclusion
Support was modified to not pass the system CLASSPATH to the
jvm classpath option.

APAR PQ76596 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ76596
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-07-21
Closed date 2003-08-30
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ79825    UP03/09/10 P F309

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ76596.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ76596
IBM Group: Software Group
Modified date: Oct 3, 2003