PQ75423: CUSTOMER STOPS AN APPLICATION IN A SERVER AND GETS A MESSAGE "THE OPERATION DID NOT COMPLETE IN THE EXPECTED AMOUNT OF TIME" | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer using the AdminConsole, selects " Enterprise Applications ", then selects an application and hits the STOP button. He sees the " please wait " icon and after a couple of minutes a message pops up on the Admin console, "The operation did not complete in theexpected amount of time. It may have completed successfully. Check thelogs for details" The application was successfully stopped. MD17258Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: All users of WebSphere Application Serv * * V5.0 for z/OS * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer using the administrtive console, selects "Enterprise Applications", then selects an application and hits the STOP button. He sees the "please wait" icon and after a couple of minutes a message pops up on the administration console, "The operation did not complete in the expected amount of time". This problem is caused by the fact that one or more MBeans are being deactivated within the servant before the respective MBeans issue the j2ee.state.stopped notification. This is not a problem in the WebSphere/Distributed environment, because the notification service does not police the fact that the MBean is not registered when it issues the notification. However, this causes a problem in the WebSphere for z/OS environment. Within z/OS, a notification issued by a servant MBean is forwarded to the associated MBean proxy (residing in the controller). In this case, the MBean proxy has already been unregisted (because the associated servant MBean has been unregistered) and the notification is discarded (because there is no MBean proxy to handle the notification).Problem conclusion The admin.jmx component has been modified to simply reissue a notification in the case where it is attempting to forward a notification from a servant MBean to its associated MBean proxy and the associated MBean proxy is not currently registered within the controller. APAR PQ75423 is associated with SERVICE LEVEL W500103 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: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ75423.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 #: PQ75423
IBM Group: Software Group
Modified date: Sep 9, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.