Fixes are available
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
After a "Start" of the IHS admin Server (adminctl start) there should be at least 3 processes running in UNIX: 1 Root Process with parent of 1 2 Root Process with Parent of another Admin.conf root process 3 admusr process which is the (User directive in the admin.conf) The output of "ps -ef | grep admin.conf" at the time of these failures reveals that the 2nd root process is gone. This process handles the adminSocket communication for the Start and Stop. The problem is that the main Apache/IHS root parent process has no way of knowing that this root process is gone.
Local fix
The temporary solution is to restart the IHS Admin server (i.e. adminctl start). However, better logging of this situation is needed.
Problem summary
**************************************************************** * USERS AFFECTED: All WebSphere Application Server web * * server status users * **************************************************************** * PROBLEM DESCRIPTION: The Web server status in the * * Application Server Administrative * * console is incorrect. The IBM HTTP * * Server has start or stopped and * * the Web Server status in the WebSphere * * Application Server Administrative * * console does not reflect the updated * * status of the IBM HTTP Server. * * * * * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server version 6.0.2 and 6.1 Web server status in the Web server collection panel of the Administrative Console for Application Server has displayed incorrect status. The incorrect status was caused due to a timing failure between the request to stop the Web server and the acquistion of the Web server status. Changes have been made to add a loop to Web server status check. We have encountered a problem when the Special Administration Server root process has terminated yet the IBM Administration Server continues to run. We added changes to the IBM HTTP Server Administration Server Root Process to terminate the IBM HTTP Server Adminsitration Server in the Administration Server root process exit. We also encountered a problem where the IBM HTTP Server Administration Server has initialied yet the socket file, which is critical for the Start/Stop function of IBM Administration Server, has a fatal error. We have changed IBM HTTP Server Administration Server code so that IBM HTTP Server Administration will fail to initialize if the Socket file can not be created. Error messages will be written to the IBM HTTP Server Amdinsitration Server log.
Problem conclusion
This fix applies to both IBM HTTP Server version 6.0 and WebSphere Application Server version 6.0.2 or 6.1. However the patches are not dependent, meaning you can apply the fix to IBM HTTP Server and not apply to Application Server and the converse.
Temporary fix
Comments
APAR Information
APAR number
PK34981
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-11-21
Closed date
2007-02-01
Last modified date
2007-07-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WEBSRV
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
28 December 2021