PQ47682: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ47682 addresses the following * * problems in WebSphere Application * * Server V4.0 for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ47682 addresses the following problems in WebSphere Application Server V4.0 for z/OS and OS/390: A race condition during bootstrap may occur, which could lead to a failure of the Naming Server with an OBJECT_NOT_EXIST exception. Interop is not possible with some other java ORBs, due to padding in the operation in a request to align the parameters. Migration job BBOMMIG does not report error conditions in step 1. when the configuration xml file that was created using prepare for coldstart with CB3.02 is migrated to the WAS V4.0 level of the product. Errors can be seen in the joblog of Step 2, but they do not get properly reported as errors using JCL mechanism. The job continues to Step 4. Comments in jcl BBOMMIG, refer to a plan #PLAN# which is bound to the DB. This plan MUST be a new plan. The job documentation was not clear enough about the fact that it must be a new plan. PATH environment variables not migrated by job BBOMMIG, from either the .env files or the configuration XML. Trace messages are going to operator console (WTO) that should NOT be sent to the console. nullPointerException on line 377 in WS390ContainerManager.keyToObject in the application Server Region, will cause the client code to see an error CORBA::INTERNAL with minor code C9C257C7. Messages that reveal 1.1 bean level artifact names are not being used by the generated classes, will be re-routed from the console to the error log or CTrace output. Transactions not marked for rollback only when system exceptions cross a business method boundary. Given an application that updates 25-30 DB2 tables as part of a unit of work. All the containers in the application have a transaction policy of "Required". Without doing explicit start, stop, or rollback of transactions on the client or in the server code. Relying on the framework to control the transactional context. This application failed with a -904, resource unavailable on one of the indexes while doing a insert. The db2 failure caused a CORBA:;INTERNAL error to be thrown. The updates that occurred prior to this failure were NOT rolled back, they were committed!Problem conclusion Code has been changed such that the majority of the bootstrap is run in a Systems Management Server Region. By doing this the race condition is averted. Code has been changed in the following parts: bbomboot.cpp, bbomib86.cpp, bbomsbo8.cpp, bbomsco.cpp, bbooboai.cpp, bboosmoi.cpp, bbouenus.cpp, bbomboot.h, bbomdtd.h, bbomib86.ih, bbomsco.h, bboosco.h, bboosmo.idl, bboosmo.idl,and bbouenus.h Code has been changed in modules bboocomm.cpp and bboobokc.cpp to pad the object key if necessary, rather than padding the operation. This will allow other java ORBs to match when comparing the operation. The shellscript bbommig.sh that's being executed by the migration job (BBOMMIG) step 1 was modified to report a proper return code to the job. The job was modified to make sure that Step 2, which retrieves the output from the shellscript that has been executed in Step 1, is executed and the job terminates afterwards. Comments in job BBOMMIG have been changed where the plan that is being bound is now called #NEWPLAN#, and a warning note has been added, to let the customer know that this should be a new, not an existing plan name. Code has been changed in the following parts, to include the PATH information during migration. bbommig.jar, bbommig.srcjar, bbompat.prepcpp, bbompdb2.prepcpp and bbompdb2.h Part bborjtr.cpp was updated to direct only Tr type AUDIT to WTO. The remainder of the Tr type messages will be sent to CTrace or error log. Class BeanId was updated to set the primary key when the deserialize method is called on class BeanId. Code has been changed to route the messages that reveal 1.1 artifact names are not being used by the generated classes off of the console, instead to the error log or CTrace. When a system exception is thrown and travels across a remote method boundary of an object, the transaction that is currently active on the thread of execution should be marked for rollback only. Without this corrective service it is possible to lose transactional updates when a system exception is thrown and caught. In particular, failures in data object updates can raise system exceptions. If business object code is written to catch these exceptions, the transaction is committed even though the data object failed. Support was added to mark the active transaction for rollback only when a system exception or undefined user exception travels across a remote method boundary. A remote method is considered to be any method that is driven through a local or remote proxy. ---------------------------------------------------------------- A change is required 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/ . . The following document must change: . Document Name: WebSphere Application Server V4.0 for z/OS and OS/390 Messages and Diagnosis Document Number: GA22-7837-00 ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0719E Bootstrap error. Could not create default administrator Explanation: During bootstrap, create of the Systems Management default administrator failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0720E Bootstrap error. Could not import configuration XML file Explanation: During bootstrap, import of the configuration xml file failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0721E Bootstrap error. Could not create initial references Explanation: During bootstrap, create of the Systems Management initial references failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0722E Bootstrap error. Could not commit the imported configuration Explanation: During bootstrap, commit of the configuration imported from XML failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0723E Bootstrap error. Could not process previously installed EAR files Explanation: During bootstrap, processing of previously installed EAR files failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0724E Bootstrap error. Could not create the Systems Management name space Explanation: During bootstrap, create of the Systems Management name space failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0725E Bootstrap error. Could not create naming registration entries Explanation: During bootstrap, create of the naming registration entries for the imported configuration failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0726E Bootstrap error. Could not register CB servers in naming Explanation: During bootstrap, registration of the CB owned servers failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0727E Bootstrap error. Could not cleanup configuration Explanation: As last step of bootstrap, some housekeeping and cleanup is done in the Systems Management data base. This step failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0728E Bootstrap error. Could not get Systems Management server region SMO Explanation: Building a direct, non transactional server region object for Systems Management failed. User Response: Check console messages and job log for further information on the error. ________________________________________________________________ Chapter 12, pg. 301 (new message) BBOU0729E Bootstrap error. Could not create upper tree structure for WS naming Explanation: During bootstrap, create of the upper tree structure for WS naming failed. User Response: Check console messages and job log for further information on the error. ---------------------------------------------------------------- APAR PQ47682 is associated with SERVICE LEVEL W400010 of WebSphere Application Server V4.0 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: UQ53715 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ47682
IBM Group: Software Group
Modified date: Jun 4, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.