PK05222: WHEN STOP COMMAND ISSUED FOR THE CONTROL REGION, IT TAKES A LONGTIME BEFORE THE SERVANT REGION AND THEN THE CONTROL REGION STOP.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When Stop command is issued for WebSphere Control Region, it
takes up to 180 seconds before the Servant Region and after that
the Control Region to stop. When Administrative Console is
stopped first, then Control Region and Servant Region come down
as expected.
Local fix
Make sure the adminconsole on the application server is stopped
before the Stop is issued for the Control Region. Commands
1. get the appmanagement mbean as follows:
set mbean [$AdminControl queryNames type=AppManagement,*]
2. Then invoke the stopapplication method on the mbean providing
the name of the application as follows:
$AdminControl invoke $mbean stopApplication {adminconsole null
null}
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: A delay of at least three minutes       *
*                      occurs when an Application Server       *
*                      running the Administrative Console      *
*                      application is stopped.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the base server (in Base) or Deployment Manager (in ND)
running the Administrative Console is stopped, an unnecessary
delay occurs during communication of the event between the
servant and controller.  Specifically, the controller awaits
a response from a servant that is already shutting down and
will never respond.  Eventually, timeout occurs and the stop
completes.

If tracing is enabled, the CORBA INTERNAL error "server
shutdown while waiting for JMX response, minor code:
C9C25747 completed: Maybe."
Problem conclusion
The controller will no longer attempt this communication if
the servant is already shutting down.

APAR PK05222 is associated with SERVICE LEVEL W502030 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK05222
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-05-03
Closed date 2005-05-23
Last modified date 2005-06-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK03726    UP05/05/28 P F505

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK05222.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 #: PK05222
IBM Group: Software Group
Modified date: Jun 2, 2005