Symptom

The following error appeared when attempting to start the WebSphere application server.

bash-3.00# ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
       /usr/IBM/ND/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. startServer.log,
       SystemOut.log(or job log in zOS) and other log files under
       /usr/IBM/ND/WebSphere/AppServer/profiles/AppSrv01/logs/server1
       should contain failure information.

In addition to the following error, no data was written to WebSphere system logs to help diagnose the issue.

With no logging information available, it was necessary to attempt a server startup –trace option enabled. When the server failed to start, the following was logged into startServer.log:

[10/11/06 10:13:16:574 CDT] 0000000a ResourceLocat 3   /usr/IBM/ND/WebSphere/AppServer/profiles/AppSrv01/config/cells /scp5501Cell02/clusters//variables.xml not found
                 java.io.FileNotFoundException: /usr/IBM/ND/WebSphere/AppServer/profiles/AppSrv01/config/cells/scp5501Cell02
/clusters/variables.xml (A file or directory in the path name does not exist.)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:135)
        at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createFileInputStream
(URIConverterImpl.java:462)
        at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createInputStream
(URIConverterImpl.java:424)
        at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:829)
        at com.ibm.websphere.resource.WASResourceImpl.load(WASResourceImpl.java:61)
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:349)
        at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:92)
        at com.ibm.ws.runtime.service.ConfigRootImpl.
getResource(ConfigRootImpl.java:325)
        at com.ibm.ws.runtime.service.ConfigRootImpl.
getResource(ConfigRootImpl.java:291)
        at com.ibm.ws.runtime.service.ConfigRootImpl.
getResource(ConfigRootImpl.java:272)
        at com.ibm.ws.runtime.config.ResourceLocatorImpl.
getResource(ResourceLocatorImpl.java:46)
        at com.ibm.ws.runtime.component.VariableMapImpl.
reload(VariableMapImpl.java:144)
        at com.ibm.ws.runtime.component.VariableMapImpl.
initialize(VariableMapImpl.java:103)
        at com.ibm.ws.management.tools.WsServerLauncher.
initializeRepositoryAndLauncher
(WsServerLauncher.java:380)
        at com.ibm.ws.management.tools.WsServerLauncher.
runTool(WsServerLauncher.java:257)
        at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:261)
        at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:112)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
        at sun.reflect.DelegatingMethodAccessorImpl.
invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:615)
        at com.ibm.ws.bootstrap.WSLauncher.main
(WSLauncher.java:263)

This error occurs when you try to run a standalone server instance and the server is not part of a cluster. The server assumes that the default behavior is to belong to a cluster.

Solution

To resolve this issue you need to install WebSphere Fix Packs, as follows:

• Download and install the UpdateInstaller for WebSphere 6.1
• Download and install the applicable Fix Packs. 

 Download and Install the UpdateInstaller 

1. Go to http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24012718 to access the download site.
2. Scroll down to the Download Package table and select the download for your specific operating system. Then click the I agree link on the license statement, the download window appears.
3. Save the .zip file to a location on your hard drive.
4. Unpack the .zip file and run install.exe to start the install wizard. UpdateInstaller is installed in /usr/IBM/ND/WebSphere/UpdateInstaller.

Go to the next section to download and install the Fix Packs.

 Download and Install the Fix Packs 

1. Go to http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK26941 to access the appropriate Fix Packs.
2. Select one of the following Fix Packs depending on your operating system:
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for AIX
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for i5/OS
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for HP-UX
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for Linux
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for Solaris
   6.1.0.2: WebSphere Application Server V6.1.0 Fix Pack 2 for Windows
3. From one of the above links, scroll down to the Download Package table and select he appropriate Download Option. . Then click the I agree link on the license statement, the download window appears.
4. Save the .zip file to a location on a local drive.
5. Unpack the file and save the Fix Pack to the Maintenance directory under the UpdateInstaller.
   ${WAS_HOME}/UpdateInstaller/maintenance
6. Make sure WebSphere and all the nodes are shut down.
7. Run update.sh to install the Fix Pack.
8. Restart WebSphere.