PQ86945: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V5.0 for z/OS.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ86945 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS: * * * * (185616.1) Mismatched * * backendid/datsource can lead to * * possible data corruption issues * * * * (185616.2) CMP Bean code that is mapped * * to a backend different than the backend * * it was generated for may cause data * * integrity problems. * * * * (MD19360) When stopping or uninstalling * * an application that contains an MDB, * * the listeners in the Controller Region * * are not removed. This is a problem if * * an application with the same name as * * the one previously removed is installed * * with a similarly named MDB that is * * listening to a different destination. * * Messages sent to that destination * * will not be delivered to the MDB. * * * * (MD19390) Abend 0C4 reason code 4 in * * controller region during inbound * * response processing. * * * * (MD19399) When using admin functions to * * stop a server, the message "BBOO0223I * * Failed to stop the process" may appear * * even though the server stopped. * * * * (MD19620) After building a cluster, the * * server is unable to start. * * * * BBOM0053E FOR ENVIRONMENT VARIABLE * * server_generic_uuid A VALUE * * MUST BE ASSIGNED * * * * (MD19724) Optimization for PQ76646 was * * regressed in the W502000 service level. * * The impact is a performance * * degradation when security is enabled * * for a Local OS registry when * * SAF Authorization is chosen. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ86945 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (185616.1) A backendid is a piece of data defined in the beans extensions metadata. Backendids identify the target database persistence code for a given application. It is possible to create an application that contains multiple backend persistence codebases. Depending on the setting of the backendid a given persistence class will be selected at run time for interaction with the backing datasource defined on the server. Therefore it is possible to install an application whose backendid is set to DB2NT (lets say) into an environment with a DB2 for z/OS datasource (lets say) selected as its resource. The backendid is used to select the persistence code to be used during runtime and this fact can lead to data corruption issues when the chosen persistence code does not include specilized locking semantics that the target resource depends on to maintain consistency. (185616.2) The locking behavior of SQL generated by the persistence manager is determined by the backend id of the backend that the CMP code was generated for. If this generated SQL is then executed against a different backend, unexpected locking behavior can occur which may lead to data integrity problems. (MD19360) The installation of an application that contains an MDB after uninstalling an application named the same as the one being installed, causes messages sent to the destination that the MDB is listening to not to be delivered. For example, if MyApplication contains MyMDB and it is listening to MyQueue, then removing MyApplication and installing another application named as MyApplication with MyMDB and listening to YourQueue, without restarting the server, will cause messages sent to YourQueue to stay in that queue. (MD19390) ABEND0C4/ABENDS0C4 reason code 4 in the comm_inbound_response method while using the orbr object that was freed by another thread. Send failed first time through loop in comm_cr_sclt_locate_request method. Second time through loop send worked but went back to caller indicating no send was done. Since caller thought no send was done the orbr object was freed out from under another thread that was processing the inbound response. Dump Title: COMPON=WEBSPHERE Z/OS, COMPID=5655I3500, ISSUER=BBORLEXT,ABEND IN BBOBOA /comm_inbound_response( TraceBack ORB_Request::comm_inbound_response(GIOP_Message*,unsigned ch +00030DBC BBOBOA Exception ACR_ExecutionThread::ProcessInboundResponse(acrwObj*) +0000018E 1794 BBOBOA Call ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*) +0000079E 5172 BBOBOA Call ACR_ExecutionRoutine +00000122 5555 BBOBOA Call CEEPGTFN 0C50A098 +0000005A CEEPLPKA Call CEEOPCMM 0091A9A0 +00000932 CEEBINIT UQ73599 Call (MD19399) Due to an uninitialized variable, the return code from the service which stops the server may report a failure even when the process was really stopped. (MD19620) The administrative console was choosing the wrong server when building a cluster, and incorrectly building it out of another server. This only occurs when you have two servers on two distinct nodes, such that each server has an identical server long name. The server short name is not affected by this. (MD19724) In Service Level W500104, an optimization was done to avoid issuing Unix Systems Service APIs to retrieve UID and GIDs when SAF authorization is performed for a Local OS Registry. Retrieving these values cause RACF to issue I/Os to DASD each time a credential is built. These values are not required when SAF authorization is done. The mainline path for servlet authentication moved the creation of the credential to a wrapper class in W501000, and this optimization for SAF credentials was lost.Problem conclusion APAR PQ86945 fixes various defects in WebSphere Application Server V5.0 for z/OS. (185616.1) Modified the runtime to ensure that the backendid specified on an application is correct for the datasorce that the application utilizes. If there exists a mismatch, the method dispatch will not be allowed to proceed and an exception will be delivered back to the caller. This exception will indicate that there currently exists a mismatch between the backendid and the configured datasource. That mismatch will need to be rectified before that method will be allowed to run to completion. (185616.2) The WebSphere Application Server for z/OS Relational Resource Adapter was modified to provide backend id checking at runtime. The adapter will check the backend id supplied by the persistence manager against the backend id for the backend that is actually in use and will inform the persistence manager if these values are incompatible. Defect 185616.2 shipped in APAR PQ86945 requires a change to documentation. Changes to the WebSphere Application Server Information Center will be made. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The following messages will be added: Message identifier - DSRA8210W Explanation: The database which is represented by the backend ID does not match the datasource connected to it. User Response: Use a backend ID which matches the datasource to deploy the EJB, or change the datasource to match the backend ID. (MD19360) Stopped and removed connection browsers in the Controller Region for a specfic MDB that was stopped or removed due to stopping or removing the application that contains it. (MD19390) Updated comm_cr_sclt_locate_request to indicate a send was done if the second send was successful. (MD19399) Updated bbo3cmds.cpp to initialize ret_code to ok. (MD19620) The administrative console was modified to use the correct server based on the Node/Server pair which is unique in a Cell. (MD19724) Modified the UserRegistryImpl wrapper class to call the optimized SAFRegistry createCredential class when a local OS Registry Credential is generated. APAR PQ86945 is associated with SERVICE LEVEL W502006 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: UQ87201 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ86945.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 #: PQ86945
IBM Group: Software Group
Modified date: May 5, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.