PQ56524: 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 PQ56524 addresses various problems * * in WebSphere Application Server V4.0 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ56524 addresses the following problems in WebSphere Application Server V4.0 for z/OS and OS/390: (MD12360) The System Management End User Interface (Administration and Operations applications) also known as the SM EUI cannot correctly handle symbolic names in JNDIName field. When symbolic name such as "&SRVNAME" is used within JNDIName field of SM EUI during Install J2EE Application step, SM EUI can not handle this string properly. If a J2EE application (*.ear) file is saved with symbolic JNDIName, SM server is unable to correctly parse the JNDIName & substiture correct name for the symbolic name. (MD12183) When running our client code under the WebServer with the WebServer environment configured to a non-IBM-1047 code page, a CORBA::Internal exception is raised from bboocds.cpp in IBM_name_to_OSF() with a minor code of C9C2119D. Client code pages other than IBM-1047 are not supported for C++ clients. However, for processing from a Java client, for example, one running under the WebServer, the code page of the process is not relevant. Therefore, the code page processing done in building the GIOP messages should not be subject to the limitations imposed on C++ clients. Simply put, the code which generates the exception should be skipped in these cases. (MD11622) The IBM JDK shipped IDLJ stubs that directly conflict with WebSphere Application Server V4.0 for z/OS and OS/390 SHASTA stubs. Specifically, the JDK shipped IDLJ Stubs and bindings for org.omg.CosNaming.NamingContext without shipping a corresponding ObjectStub. This exposed a path whereby a Java application could attempt to converse directly with a native C++ Server (CosNaming) without going through Shasta first (no ASCII/EBCDIC translation, etc.). Our Java ORB Implementation did not adequately support IDLJ stub invocations. We expected all method invocations to come from our Shasta stubs, which extend the class SOMBase. Attempting to narrow or resolve the IDLJ stub would fail with a CORBA::BAD_PARAM exception, since the IDLJ stub did not extend SOMBase, as we expected it to. ( PQ54184) When the System Management End User Interface (Administration and Operations applications) also known as the SM EUI is invoked to prepare the active conversation for a coldstart a dialog appears that tell the administrator about the consequences and offers him the facility to change the daemon ip name already in the configuration data. This is offered in form of a checkbox, and when this is checked, an entry field is displayed where the new daemon ip name can be entered. When this entryfield is made visible, the buttons at the bottom of the dialog are pushed out of the visible area of the dialog and cannot be accessed without resizing the dialog. The problem is that the JFC layout manager that is used for arranging the controls in the dialog has changed it's behaviour between the JDK level that was used when it was developed (1.1.8) and the actual JDK 1.3. Previously there was also some space reserved in a dialog for invisible components, like in this case the entryfield for the daemon ip name. Now this is no longer the case and this is why the dialog is now too small when the entryfield is made visible.Problem conclusion APAR PQ56524 provides the following problem resolution: (MD12360) The System Management End User Interface (Administration and Operations applications) also known as the SM EUI is now able to handle symbolic names within JNDIName field during Install J2EE Application process. Not only '&' is handled correctly, but characters such as '<', '>', ''', and '"' are also handled properly with this support. (MD12183) Support was added to recognize the requests which flow from Java clients to modify their processing with respect to code page negotiation to ignore the native code set for the space as it is not relevant. (MD11622) Methods were added to our ClientDelegate and ORB implementations to handle the DII IDLJ invoke path. Support was also added to correctly cast and narrow IDLJ Stubs within our Shasta/C++-based runtime. A fix was obtained from the JDK (APAR PQ52781) to support EBCDIC code pages in Java. ( PQ54184) To resolve the problem in the System Management End User Interface (Administration and Operations applications) also known as the SM EUI where the dialog is too small when the entryfield for the daemon ip name is made visible, the code was changed to explicitly reserve space for the entryfield. The following publication was revised as a result of APAR PQ56524: ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 Messages and Diagnosis GA22-7837-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: http://www.ibm.com/software/webservers/appserv/ Chapter 13, pg. 273 and following (new minor codes): ________________________________________________________________ C9C21260 Explanation: Attempted to invoke a request that doesn't exist. Somehow invoke_request was called without create_request being called first. User Response: IBM Internal Only ________________________________________________________________ C9C21261 Explanation: The Java to C++ ORB Bridge caught a system exception which it was unable to identify and pass back to Java. This exception is substituted since the bridge can't properly pass back an exception it can't identify. This should only happen if we somehow mangled the exception or someone passed us something outside the set of standard system exceptions. ORB detailed tracing should probably show the bogus exception User Response: IBM Internal Only ________________________________________________________________ C9C21262 Explanation: Attempted to invoke a request that doesn't exist. The Java native method jorbinvokeRequest was driven before (or without) jorbrequest, so no request object exists. User Response: IBM Internal Only ________________________________________________________________ Chapter 13, pg. 385 and following (new message) ________________________________________________________________ C9C21265 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ C9C21266 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ C9C21267 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ C9C21268 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ C9C21269 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ C9C2126A Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ Chapter 13, pg. 401 and following (new minor codes) ________________________________________________________________ C9C21C49 Explanation: The WebSphere Application Server for z/OS and OS/390 ORB is not initialized. An IOR can not be created from an object if an ORB is not available. User Response: Check error logs for failure of the ORB to initialize. If there are not any ORB initialization failures then the initialization will need to be added to the client code. ________________________________________________________________ C9C21C4A Explanation: The reference object used to link C++ and Java objects together is null. If the SOMRef is null, and IOR can not be obtained. User Response: IBM Internal Only ________________________________________________________________ C9C21C4B Explanation: A CORBA Object pointer was not stored in the link object. If the object pointer is not present an IOR can not be obtained. User Response: IBM Internal Only ________________________________________________________________ C9C21C4C Explanation: An ORB Proxy pointer can not be obtain for a CORBA Object. An IOR can not be obtained. User Response: IBM Internal Only ________________________________________________________________ C9C21C4D Explanation: The IOR resulting from a call to object_to_IOR was null. A vaild IOR could not be created. User Response: IBM Internal Only ________________________________________________________________ C9C21C4E Explanation: The IOR for an object was invalid. User Response: IBM Internal Only ________________________________________________________________ Chapter 13, pg. 463 and following (new minor codes) ________________________________________________________________ C9C257EE Explanation: The ORB received an exception from the J2EE container while trying to load an IDLJ stub. User Response: Correct the application. ________________________________________________________________ C9C257AA Explanation: The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request. User Response: IBM Internal Only ________________________________________________________________ C9C257A9 Explanation: The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request. User Response: IBM Internal Only ________________________________________________________________ C9C2576C Explanation: getServiceContextList is not implemented in this implementation of ClientResponse. User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support. ________________________________________________________________ C9C2576D Explanation: getRequestId is not implemented in this implementation of ClientResponse. User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support. ________________________________________________________________ C9C2576E Explanation: getForwardedIOR is not implemented in this implementation of ClientResponse. User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support. ________________________________________________________________ C9C2576F Explanation: peekUserExceptionId is not implemented in this implementation of ClientResponse. User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support. ________________________________________________________________ C9C2577F Explanation: An invalid ClientDelegate was used to drive a request. User Response: IBM Internal Only ________________________________________________________________ C9C2577E Explanation: An unexpected error has occurred in a J2EE server during execution of a J2EE request. User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred. ________________________________________________________________ C9C2577D Explanation: An unexpected error has occurred in a J2EE server during execution of a J2EE request. User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred. ________________________________________________________________ C9C2577C Explanation: The object given to the ORB had an incorrect delegate while trying to load a IDLJ stub. User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred. ________________________________________________________________ APAR PQ56524 is associated with SERVICE LEVEL W400059 of WebSphere Application Server V4.0 for z/OS and OS/390.Temporary fix Comments **** PE02/03/13 FIX IN ERROR. SEE APAR PQ58919 FOR DESCRIPTION **** PE02/03/22 PTF IN ERROR. SEE APAR PQ58919 FOR DESCRIPTION
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ62233 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 #: PQ56524
IBM Group: Software Group
Modified date: Mar 22, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.