E1: WAS: Troubleshooting Errors When Starting Websphere Application Server (Doc ID 1163184.1)

Last updated on AUGUST 21, 2024

Applies to:

Purpose

*Purpose
Enter a clear description of what the document is trying to achieve.

This document contains known issues when starting application server like JAS Instance or Server1 or nodeagent in Websphere Application Server.

Most of the time, the error is logged in Websphere's SystemErr.log and SystemOut.log, which can be found in:

X:\IBM\WebSphere\AppServer\...\logs

 There are various ways to start Websphere Application Server:

1. You can setup Windows service to start the application server. Refer to <Document 635841.1>.
2. The typical way to start it is to use the batch files, which comes with Websphere installation. Below is the example on how to start and stop application server from command line.
    
   
   • • To start

   <IBM WAS HOME>\profiles\...\bin\startserver <JDE App Server Name>

   • • To stop

   <IBM WAS HOME>\profiles\...\bin\stopserver <JDE App Server Name>

   • • To check server status

   <IBM WAS HOME>\profiles\...\bin\serverstatus <JDE App Server Name>

   Note: You can create your own script to call these commands.
    
3. Starting Tools Release 8.97 and above, use Server Manager Console to start the application server.

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.