My Oracle Support Banner

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

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
*** check for relevance 31-JAN-2012 ***
***Checked for relevance on 1-DEC-2014***

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

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 Scenario 1:  Error "Premature End Of File" Message When Starting JAS Instance
 Scenario 2:  Conflicting HTTP transport setting is preventing application server startup
 Scenario 3:  EA_JS_nn Cannot Be Started Because it is Installed on a Different Server
 Scenario 4:  Websphere Node Agent Show Not Started in Admin Console but it Shows Started in Command Window
 Scenario 5:  JAS Servlets Stop Working After Changing the Domain in the Network
 Scenario 6:  Websphere Does not Start, Failing to Authenticate to IBM Directory Services
 Scenario 7: Unable to start one of the E1 Web instances
 Scenario 8: Websphere Application Server does not start properly

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