PQ83203: CALL STACK APPEARS IN THE CONTROLLER TRACE - EXCEPTION STATING THE CONTROLLER IS UNABLE TO CONNECT TO THE SERVANT DURING INIT. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description ConnectorNotAvailableException appears up to 15 times in a stack trace. A call stack appears in the the Controller trace due to an exception stating the Controller was unable to connect to the Servant during initialization. These messages can be ignored providing there is not any problem and the messages were found by reviewing the logs. In this special non-error case, the servant is able to contact the Controller via a CORBA request; however, the Controller is unable to submit a CORBA request back to the Servant to complete the handshake. This is not an error. The Controller is not able to contact the Servant via a CORBA request because the Controller is not yet aware how to reach the Servant. This will address removing the confusing stack traces when there is no true problem.Local fix These stack traces can be ignored in this special non-error situation.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Controller is unable to connect * * to Servant during initialization. * **************************************************************** * RECOMMENDATION: * **************************************************************** A call stack appears in the the Controller trace due to an exception stating the Controller was unable to connect to the Servant during initialization. The servant is able to contact the Controller via a CORBA request, however the Controller is unable to submit a CORBA request back to the Servant to complete the "handshake".Problem conclusion This is not an error. The Controller is not able to contact the Servant via a CORBA request because the Controller is not yet aware how to reach the Servant. Once the Servant completes initialization, the Controller discovers it (thru WLM), and can submit requests to it. Until that time, the Servant attempts to "handshake" with the Controller once every minute for the first 15 minutes, then once every 5 minutes thereafter. The exception stack traces should not have appeared in the trace. The code that caused the stack traces to appear has been removed. The following publication was revised as a result of APAR PQ83203: ________________________________________________________________ WebSphere Application Server V5 for z/OS Messages and Codes GA22-7915-00 ________________________________________________________________ This APAR requires changes to documentation. 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 04, pg. 003 (new message) Message identifier - BBOJ0080E Error encountered during initialization {0}. Explanation: A Websphere for z/OS server encountered an error during server startup. User Response: Exception details accompany error message. APAR PQ83203 is associated with SERVICE LEVEL W502001 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: swg1PQ83203.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 #: PQ83203
IBM Group: Software Group
Modified date: Feb 4, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.