PQ62333: ADMIN CONSOLE INDICATES ENTERPRISE APPLICATION IS STARTED, HOWEVER, WHEN CHECKED WITH WSCP IT SHOWS STOPPED.

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Here is the test senerio for WSCP:

wscp> EnterpriseApp show /EnterpriseApp:intlbl/
{Name intlbl} {FullName /EnterpriseApp:intlbl/} {CurrentState
Stopped} DesiredState Running} {StartTime 1021486630789}
{OrigEarFile /apps/apl/intlbl/servlets/intlbl.ear} {OrigNodeName
rcdaix10}
The output shows stopped but the console shows Running.
Local fix
If the Enterprise Application is running, WSCP will show stopped
as the current status, however, it wil lhave a StartTime. If the
Enterprise Application is stopped, there will be no StartTime.
So by viewing the StartTime field, the customer can determine if
the Enterprise Application is actually running.
OR
Use the Console and View Status.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users running   *
*                 4.0.2 or later using WSCP to check current   *
*                 status of enterpriseApp or module            *
****************************************************************
* PROBLEM DESCRIPTION: Admin console indicates enterprise      *
*                      application is started/running,         *
*                      however when checked using WSCP is      *
*                      shows it is stopped.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Here is the test senerio for WSCP:
wscp> EnterpriseApp show /EnterpriseApp:intlbl/
{Name intlbl} {FullName /EnterpriseApp:intlbl/} {CurrentState
Stopped} DesiredState Running} {StartTime 1021486630789}
{OrigEarFile /apps/apl/intlbl/servlets/intlbl.ear}
{OrigNodeName rcdaix10}

The WSCP output shows stopped but the console shows "Running"
by right-clicking on the application->show status on the GUI.

Issuing a WSCP show command on a module also returns incorrect
state.
Problem conclusion
Application of eFix PQ62333 allows customer to use WSCP to
learn the status of the EnterpriseApps by issuing the "show"
command and look at the "currentState" attribute.

***NOTE****
The console "show status" on Application is really reporting a
table with status of each server each module is installed on.

The reason for this is because when the App is installed on a
ServerGroup, various permutations of the state of servers and
modules can exist on the EnterpriseApp.

Consequently, WSCP show on EnterpriseApp reports status of the
App based on the status of servers and modules:

An EnterpriseApp is "running" if at least one of the Modules
it contains is running.

A Module is "running" if all the servers it is installed on
are running.

This fix also address same incorrect current status reported
on Modules using WSCP Module show command.
Temporary fix
provided customer with eFix PQ62333 and waiting for customer fix
 confirmation
Comments
APAR information
APAR number PQ62333
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-06-17
Closed date 2002-07-18
Last modified date 2002-07-18

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62333
IBM Group: Software Group
Modified date: Jul 18, 2002