PQ54032: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0.1 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ54032 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ54032 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: MD11132 When using the SM Scripting API "removeApplicationFamily" and specifying a non-existing server, the following messages are shown: BBON3199E Method removeApplicationFamily failed. BBON1000E The Application Family object, <family-name>, could not be found. These error messages are incorrect for the problem. The correct error messages for this situation are: BBON3199E Method removeApplicationFamily failed. BBON1000E The Server object, <server-name>, could not be found. MD12220 Script parameters of the form name='value' ... cause a Java exception StringIndexOutOfBoundsException when closing apostrophe is omitted. This error situation should result in an appropriate error message being issued instead. MD12477 The Stop of a Control Region can hang. If the stop was performed by System Management as part of activation of a conversation, a BBON1017E message may be issued by System Management. If SMF recording is active, the thread that wakes up periodically to do SMF work may hang trying to shut down during a Stop, whether the stop was done via the MVS console command or via the WebSphere for z/OS Administration and Operation applications (also refered to as the System Management Enhanced User Interface or SMEUI). The stop can be done either by the operations or administration application via a conversation activation. The hang is because the last thing the SMF thread does as it terminates is to queue a synchronous piece of work to another thread. If that thread has already terminated as part of stop processing, the SMF thread will hang waiting for a response. MD12499 CORBA::MARSHAL exceptions occur when using Handle, EJBMetaData, Multi-object finders between J2EE client (Windows NT or 2000) and WebSphere Application Server V4.0.1 for z/OS and OS/390 server. The CORBA::MARSHAL exceptions occur because there exists a Java serialization mismatch (e.g. SUID) between client and server. The correct classes must be installed on client to resolve this problem. MD12527 ORB_Request (bbooorbr.cpp) objects (and related storage) may be leaked on HTTP Asyncio (bbocasyh.plx) requests. For an HTTP inbound request, bbooboat.cpp fails to free the related ORB_Request if comm_http_inbound_request() (bboocomm.cpp) returns with the ORB_Request indicating an error occurred (ie. isAllOK() (bbooorbr.cpp) returns false). The leak of an ORB_Request object and related storage causes a severe performance degradation due to a loop in CSRCPCEL that scans the cell pool extent queue. This problem occurs when the asynchComm_retCode (bbocsess.h) is less than 1. A zero value for asynchComm_retCode indicates that the client closed the socket or that the client has terminated without closing the socket. The failure to free the ORB_Request results in excessive real and virtual storage usage and an extremely long cell pool extent queue.Problem conclusion APAR PQ54032 provides the following problem resolution: MD11132 The code for removing an application family was modified to check for server existance and writing the appropriate error message: BBON3199E Method removeApplicationFamily failed. BBON1000E The Server object, <server-name>, could not be found. MD12220 The code for analyzing name-value pair parameters was modified to check for missing delimiters and to write an appropriate error messages: BBON3213E Unexpected syntax for parameter name parameter-name: equal sign expected. or BBON3214E Unexpected syntax for parameter name parameter-name: single quote expected. as appropriate. MD12477 The synchronous piece of work the SMF thread queues is extraneous and does not need to be done. The call which queues the work and waits for a response was removed which fixes the reported Control Region hang. MD12499 To fix the problem of CORBA::MARSHAL exceptions occuring when using Handle, EJBMetaData, Multi-object finders between J2EE client (Windows NT or 2000) and a WebSphere Application Server V4.0.1 for z/OS and OS/390 server a patch jar file "J2EEClient_NT.patches.jar" is being shipped in this APAR. Instructions to apply this patch to the client runtime is contained in file README, found inside J2EEClient_NT.patches.jar. MD12527 Code has been added to bbooboat.cpp processing to cleanup the ORB_Request in the event of a error in comm_http_inbound_request(). Also, a new message BBOU0742E will be issued to log any HTTP asyncio failures. The following publication was revised as a result of APAR PQ54032: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-02 ________________________________________________________________ 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: http://www.ibm.com/software/webservers/appserv/ ________________________________________________________________ Chapter 10, pg. 194 (new message) BBON3213E Unexpected syntax for parameter name parameter-name: equal sign expected. Explanation: This error occurs when a script parameter value of the form name='value' name='value'... is processed. The separating equal sign was expected and not found. User Response: Check your script and correct the syntax of the value for the specified parameter-name. ________________________________________________________________ Chapter 10, pg. 194 (new message) BBON3214E Unexpected syntax for parameter name parameter-name: single quote expected. Explanation: This error occurs when a script parameter value of the form name='value' name='value'... is processed. The delimiting single quote was expected and not found. User Response: Check your script and correct the syntax of the value for the specified parameter-name. _______________________________________________________________ Chapter 12, pg. 319 (new message) BBOU0742E HTTP asynchio routine failed with RV=dstring, RC=dstring, RSN=hstring, string . Explanation: WebSphere for z/OS CTL region processing detected an error during HTTP asynchio processing. Asynchio processing failed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN. User Response: See the OS/390 C++ Run-Time Library Reference or the OS/390 OpenEdition Messages and Codes for descriptions of the returned value and codes. Correct the error. If the problem persists, contact your next level of support or the IBM Support Center. ________________________________________________________________ Chapter 12, pg. 319 (new message) BBOU0745I The transaction with URID urid and XID xid has completed heuristicly. Explanation: WebSphere for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, has indicated that some resources were assigned an outcome that was different than the overall outcome of the global transaction. For example, if the overall outcome of the transaction was commit, some of the resources that were involved in the transaction have been rolled back. User Response: This message contains the transaction identifier for which the heuristic condition occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by z/OS, to determine which resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. ________________________________________________________________ Chapter 12, pg. 319 (new message) BBOU0746I The transaction with URID urid and XID xid may have completed heuristicly. Explanation: WebSphere for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, may have assigned an outcome that was different than the overall outcome of the global transaction. User Response: This message contains the transaction identifier for which the heuristic condition may have occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by z/OS, to determine if any resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. In addition, because this condition may have occurred when transactional optimizations were used, RRS may be unaware of the transactional outcome, because of a delegation of commit responsibilites to the single resource manager. In this case, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the given resource manager to determine the outcome or to correct any resources involved in the global transaction as displayed in this message. ________________________________________________________________ Chapter 13 pg. 427 (new message) C9C218D1 Explanation: Transaction rolled back during root commit. User Response: See C9C2181F. ______________________________________________________________ Chapter 13, pg. 427 (new message) C9C218D2 Explanation: IBM Internal Only. An unexpected return code was received from delegated commit 1. User Response: Contact the IBM Support Center. ______________________________________________________________ Chapter 13, pg. 427 (new message) C9C218D3 Explanation: IBM Internal Only. Transaction rolled back because a protected resource is not in the proper state for a commit. User Response: Contact the IBM Support Center. ______________________________________________________________ APAR PQ54032 is associated with SERVICE LEVEL W401006 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ60286 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ54032
IBM Group: Software Group
Modified date: Dec 4, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.