PQ95023: APPLICATION STATUS IN ADMINCONSOLE IS SOMETIMES WRONG | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Duplicate admin application management JMX notifications are sometimes issued. This hinders control over applications. Users will notice this in admin console, applications that are running may be listed as stopped; stopped applications may not be startable. When a servant region is abended and WLM starts a new servant, the applications which are started in the new servant are those which are defined to start up when the server starts (In the adminconsole, the Enable checkbox is checked, in the path Enterprise Applications > GADTest > Target Mappings > Enabled). Unfortunately this behavior can lead to problems when the system administrator has manually activated some applications which do not start up automatically and deactivated other applications which do start up automatically. In this scenario the adminconsole displays incorrect application status.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Customers may see duplicate messages * * on the WebSphere for z/OS * * Administrative Console when starting * * applications on systems with more than * * one active servant. The following * * informational messages appear on the * * WebSphere for z/OS Administrative * * Console: * * * * Application ivtApp on server server1 * * and node SY1 started successfully. * * Application ivtApp on server server1 * * and node SY1 started successfully. * * * * Customers may not be able to start * * some applications through the admin * * console. The following informational * * message appears on the WebSphere for * * z/OS Administrative Console: * * * * Duplicate application, ivtApp. * * * * Customers may not be able to stop * * some applications through the admin * * console. The following informational * * message appears on the WebSphere for * * z/OS Administrative Console: * * * * Application ivtApp not started. * * * * Customers may notice applications * * that are configured to autostart * * will continue to start when new servant * * regions are created; even after the * * applications had been explicity * * stopped in the WebSphere for z/OS * * Administrative Console. * **************************************************************** * RECOMMENDATION: * **************************************************************** JMX notifications are generated in servant regions when applications are started and stopped. These notifications travel to the ApplicationManager MBean in the controller region where the logical application state is managed. When multiple servants are active, notifications are generated in each servant region when applications are started and stopped. Notifications from different servant regions can become interleaved as they are processed in the controller region. To complicate matters, some applications may be configured to start automatically when a servant region is started. When a server's load becomes high, new servant regions may be started. These servant regions will start the applications that are configured to autostart; even when the application may have been stopped prior to the need for the new servant region. This will also cause notifications to be generated that the ApplicationManager MBean did not expect to recieve. The result is that ApplicationManager MBean can easily lose track of the correct logical state of an application in systems with multiple servants. Additionally, applications may be running in only a subset of the active servants.Problem conclusion New code has been introduced into the ApplicationManager that enables it to interpret JMX notifications from multiple servants. This allows the logical application state to be correctly maintained. New code has been introduced into the servant region intialization procedure that will prevent applications configured to autostart from starting if the applications were stopped. APAR PQ95023 is associated with SERVICE LEVEL W502017 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ95037 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ95023.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ95023
IBM Group: Software Group
Modified date: Dec 2, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.