VANWEBUI task failing with RC=0100 , java.lang.ClassNotFoundException or java.lang.NoClassDefFoundError errors.
search cancel

VANWEBUI task failing with RC=0100 , java.lang.ClassNotFoundException or java.lang.NoClassDefFoundError errors.

book

Article ID: 251002

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

When VANWEBUI starts up with RC=0100.  The output will receive additional java related message associated with the task return code. (see the messages in descriptions in resolution section)

java.lang.ClassNotFoundException

java.lang.NoClassDefFoundError

 

 

 

Environment

Release : 14.1 VANWEBUI

Component : Vantage Storage Resource Manager

Resolution

Check for mounting points and the proper ZFS (see below).

Mounting points:

Here are 3 mount points for the WebUI which need to be done correctly: 

• /u/users/cai/vantagegmi/install
• /u/users/cai/vantagegmi/runtime
• /u/users/cai/vantagegmi/webclientdb

Also, check that the CATALINA_HOME variable in the VANWEBUI STC JCL has been updated, and is pointing to the correct location (i.e., CATALINA_HOME="/cai/vantagegmi/runtime/apache-tomcat-x.xx.xx/").  This parameter is set via the STDENV DD * input control cards.    

Descriptions of error messages:

  1. java.lang.ClassNotFoundException This exception indicates that the class was not found on the classpath. This indicates that we were trying to load the class definition, and the class did not exist on the classpath.

  2. java.lang.NoClassDefFoundError This exception indicates that the JVM looked in its internal class definition data structure for the definition of a class and did not find it. This is different than saying that it could not be loaded from the classpath. Usually this indicates that was previously attempted to load a class from the classpath, The earlier failure could be a ClassNotFoundException or an ExceptionInInitializerError (indicating a failure in the static initialization block) or any number of other problems. The point is, a NoClassDefFoundError is not necessarily a classpath problem.