WebSphere Administration Server fails to start, logging java.lang.NullPointerException in the tracefile

Technote (FAQ)
Problem
WebSphere AdminServer was running fine until a new virtual host was added. After the addition of another virtual host, AdminServer will not start.
The configuration uses InstantDB as the WebSphere AppServer Repository. The following errors are logged in the tracefile.

InstantDB - Version 3.13
Copyright (c) 1997-2000 Instant Computer Solutions Ltd.
[02.09.12 22:08:00:017 PDT] 5fbf094a AdminServer A ADMS0002I:
Initializing WebSphere Administration server
[02.09.12 22:08:00:033 PDT] 8191895c DrAdminServer A SMTL0018I: DrAdmin
available on port 2,930
[02.09.12 22:08:27:486 PDT] 5fbf094a AdminServer F Encountered an
exception in the main method java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
com.ibm.ejs.container.UncheckedException: ; nested exception is:
java.lang.NullPointerException
java.lang.Throwable
at java.lang.Throwable.<init>(Throwable.java:84)
at com.ibm.ejs.ras.CBuffLogger.fatalEvent(CBuffLogger.java(Compiled
Code))
Solution

Remove the idbStore file in the $WAS_HOME/bin directory and replace the
file with the last working back up that was made. Restart AdminServer after that has been done.

If an XMLConfig export backup is available, use that to import the configuration.

Exporting and Importing using XMLConfig tool.
  1. Start the AdminServer
  2. Locate the tracefile in <$WAS_HOME/logs>
  3. Open the file and search for the string "WebSphere Administration server open for e-business"
  4. Close the tracefile
  5. Start the admin console
  6. Click on the Menu item "Console ->Export (or Import). Provide a filename such as 'xmlout' and a correct location in the file system and hit the <Apply> button
  7. Locate the file after the export(or Import) Note: After an import, always refresh the admin console.

    Alternatively, you can use the command line method. The adminServer must be running but the admin console need not be running.
    • Open the command line and change directory to <$WAS_HOME>/bin
    • Run: xmlconfig.bat (Windows) or ./XMLConfig.sh (UNIX). This will invoke the xml tool and show you the parameters you can pass to it.
      Here's an example of doing an export on both Windows and UNIX:
      xmlconfig -export <filename> -adminNodeName <primary node name>
      xmlconfig -export xmlout -adminNodeName was3

      ./XMLConfig.sh -export <filename> -adminNodeName <primary node name>
      ./XMLConfig.sh -export xout -adminNodeName was3

      To get more information on the XMLConfig tool, go to the WebSphere InfoCenter at:
      http://www-3.ibm.com/software/webservers/appserv/doc/v35/se/infocenter/index.html
      See sections, Developing Applications (section 4.2.3) and Administration (section 6.6.0.2).
    Historical Number
    PMR 23586 49R 000
    Product Alias/Synonym
    WAS 3.5.x
    WebSphere AppServer











    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting)
    Operating system(s): Windows 2000
    Software version: 3.5
    Software edition: Standard
    Reference #: 1063910
    IBM Group: Software Group
    Modified date: 2002-09-16