Systems management error: java.lang.NoSuchMethodError: _registerDatasourcesInJNDI
 Technote (FAQ)
 
Problem
Daemon01 stopped and restarted with a cold start. Systems Management Server server region receives the following error:

+BBOU0132I WS BOOTSTRAP STEP 12 Create naming registration entries
STARTING.
+BBOU0038W TERMINATING THE CURRENT PROCESS, REASON=C9C21C3E.
 
Cause
The systems management error is caused by the following:


JVM Exception Message = java.lang.NoSuchMethodError:  _registerDatasourcesInJNDI   JVM Stack Trace =   java.lang.NoSuchMethodError: _registerDatasourcesInJNDI.


The call is made to method registerDatasourcesInJNDI, which is missing. Incorrect HFS might be mounted, which results in not picking up the correct JAR files needed by system management.

 
Solution
There are two different methods with that same name:
  • C++: Stored in the DLLs/LOADLIBs,
  • Java: Stored in bbompes.jar and possibly in bbompe.jar and/or bbompec.jar. The latter appears to be the one that can not be found.

Check if the systems management server is using the correct versions of bbompe.jar, bbompes.jar, and bbompec.jar.

The main thing to check is that the CLASSPATH in the current.env for the system management server, in the SYSMGT01 directory, is not using the wrong copy. If there is a specific copy of one of those JARs listed, that could be the problem.

You can also check by the dates and sizes of these files in your HFS install directory:

  1. Change to /usr/lpp/WebSphere/lib directory.
  2. List files: ls -l bbompe.jar bbompec.jar bbompes.jar
  3. If you have the wrong copy of one of those JAR files, you might have mounted an incorrect HFS, which results in not picking up the correct JAR files needed by system management.
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1080605
IBM Group: Software Group
Modified date: Jan 7, 2005