PQ73964: REMOTE ADMINCONSOLE DOES NOT SHOW UP CORRECT STATUS AFTER PERFORMING OPERATIONS LIKE STOP/START ON APPSERVER .

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
Problem:When performing Appserver start/stop operation from
remote AdminConsole , AppServer stopped/started successfully per
log but console shows status sometimes incorrect .
Also at the right lower corner of console , progress bar never
completes when performing above oparations, though appserver
stopped/started successfully.

Reason:Because the notification for completion was never
received and the thread that is blocked on wait never times out.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 WSCP, Console, and XMLconfig to start/stop   *
*                 servers or apps.                             *
****************************************************************
* PROBLEM DESCRIPTION: Clients can hang when performing        *
*                      tasks like start/stop appserver or      *
*                      applications.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere clients (WSCP, console, XMLconfig) need to wait for
notification on completion when performing tasks like start or
stop.  If task completion notification is not received, clients
can hang due to a timeout problem.  From the user's point of
view, they can encounter scenarios such as a WSCP task completed
but the processes do not terminate or the command line never
returns.  On a remote AdminConsole, the AppServer is stopped or
started successfully but the server status is sometimes
incorrect.  Also the user may see the progress bar at 90%
completion even though the appserver stopped or started
successfully.
Problem conclusion
Clients are blocked on wait and never time out as needed
causing the client executing thread to hang or never terminate.
The solution is to correct the timeout logic to work correctly.
Temporary fix
ZE FIX ERROR 
PQ75725 03/07/21
sent customer test fix, waiting for feedback
Comments
APAR information
APAR number PQ73964
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-05-08
Closed date 2003-05-08
Last modified date 2003-07-21

APAR is sysrouted FROM one or more of the following:
PQ71967

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSCP          

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 #: PQ73964
IBM Group: Software Group
Modified date: Jul 21, 2003