PQ96034: ERROR 500 AND ADMN0034E MESSAGE ENCOUNTER WHEN STARTING SERVER FROM 2 DIFFERENT ADMINCONSOLE WEBSPHERE APPLICATION SERVER | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer encountering the following error when start the same server from two different Adminconsoles : Error 500 An error occurred while processing request: /admin/applicationServerCollection.do . Message: Server caught unhandled exception from servlet [action]: ADMN0034E: Unable to obtain a valid admin client to connect process Node_SYB from process dmgr due to exception: com.ibm.websphere.management.exception. ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke . The first console that starts the server completes while the second console will continue processing for a long time period and then display the error 500 message.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Error 500 when instances of a server * * are started by two different * * administrative console users. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following error is seen when two instances of a server are started by separate administrative console users simultaneously Error 500 An error occurred while processing request: /admin/applicationServerCollection.do Message: Server caught unhandled exception from servlet action : ADMN0034E: Unable to obtain a valid admin client to connect process "Node_<nodename>"; from process "dmgr" due to exception: com.ibm.websphere.management.exception. ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke The first attempt to start the server completes, while the second request times out and displays the Error 500 message. The second attempt fails as expected, since an instance of the server is already being started. This error is however only indicated correctly on the MVS console, while the administrative console request times out.Problem conclusion Fixes were made to correctly handle the server start failure seen by the second console user. A message is now displayed on the administrative console that indicates that the server start did not complete successfully. APAR PQ96034 requires changes to documentation. ________________________________________________________________ WebSphere Application Server V5 for z/OS Messages and Codes GA22-7915-01 _______________________________________________________________ NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library.html ________________________________________________________________ Chapter 3, pg. 125 Error (minor) codes C9C2C901 Explanation: IBM Internal Only User Response: Contact the IBM Support Center. APAR PQ96034 is associated with SERVICE LEVEL W502024 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: PQ96728 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ96034.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 #: PQ96034
IBM Group: Software Group
Modified date: Mar 1, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.