java.lang.NoClassDefFoundError running setupCmdLine.sh
 Technote (troubleshooting)
 
Problem(Abstract)
If you have two WAS_CLASSPATH entries in your setupCmdLine.sh script file; java.lang.NoClassDefFoundError error could occur.
 
Cause
If you are using scripting and have two WAS_CLASSPATH entries in your setupCmdLine.sh script file then NoClassDefFoundError error could occur. The first WAS_CLASSPATH is parsed, then the second one overwrites the first WAS_CLASSPATH.

Here is an example of what would cause an error if coded in your setupCmdLine.sh script file:
WAS_CLASSPATH="$WAS_HOME"/properties:"$WAS_HOME"/lib/bootstrap.jar:
"$WAS_HOME"/lib/j2ee.jar:"$WAS_HOME"/lib/lmproxy.jar:"$WAS_HOME"/lib/urlprotocols.jar
WAS_CLASSPATH=/u:$WAS_CLASSPATH

And the error you will receive is:

[wsStopApp] Stopping Application [provider-ear]...
[wsadmin]
@ @  @  @java.lang.NoClassDefFoundError:
com/ibm/ws/bootstrap/WSLauncher
[wsadmin] Java Result: 1
[wsStopApp] Stopped Application [provider-ear]
 
Resolving the problem
You can resolve this problem by coding one WAS_CLASSPATH statement in your setupCmdLine.sh script.
 
 
 


Document Information


Current web document: swg21188582.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Administrative Scripting Tools (for example: wsadmin or ANT)
Operating system(s): z/OS
Software version: 5.1
Software edition:
Reference #: 1188582
IBM Group: Software Group
Modified date: Oct 28, 2004