PQ59929: 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 PQ59929 addresses various problems * * in WebSphere Application Server V4.0.1 * * z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ59929 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390. (MD13170) For the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, there is no tooltip available to see long values in the environment variable tables. Also, there is a need to be able to copy a value into the clipboard when in view mode. To accomplish this, support is needed which adds a view mode to the Environment Editing Dialog so it can be used when not in edit mode. (MD11484) A WebSphere server region starts the JVM at initialization, but never calls the corresponding thread detach and JVM Destroy APIs as it terminates. For a clean termination of the server region, the JVM should be terminated cleanly as well. When a server region ends, the JVM is not terminated cleanly. This makes it difficult to gather JVM tracing information (which requires a clean termination of the JVM). (MD12385) If missing a class in an EAR file, the user can receive a generic message: BBON1201 EARFileProcessor error while processing deployment data No additional detail is provided to help determine the actual problem. More details about the root problem should be returned. (MD12846) A client can receive a CORBA::NO_PERMISSION exception from a nested EJB method call, and the exception has no minor code. The container is not properly preserving minor codes between nested EJB method calls. Therefore, the minor code is not propagated back to the client. (MD12977) Abend DC3/AbendDC3 rsncode 0205000C occurs in bbossmet when method level access checking is enabled for Systems Management homes. The Abend in bbossmet occurs when Method Level Access checking is enabled for Systems Management homes because there is no OPI on the current thread with an ACEE pointer. (MD13101) Applications using JNDI caching, with the default cache name, may return an initialContext without write permissions to LDAP even when the application properly requested an initialContext with the correct naming principal and credentials. This situation can occur as follows: By using default cache names, an application accessing the cache may store contexts in the cache which do not have write permissions to LDAP. If another application accessing the same cache obtains this cache reference, it would not be able to perform write operations on that context, even if it had requested such access. In this situation, the client would see the following exception: javax.naming.NoPermissionException: .LDAP: error code 50 - Insufficient Access Rights. The opposite situation may also occur. An application may store contexts in the cache which has write permissions. Another application which does not specify proper naming security principal and credentials may obtain this cached context and be able to write to the namespace. No exceptions are reported in this case. (MD13182) The environment variables JVM_HEAPSIZE and JVM_MINHEAPSIZE do not always yield the expected JVM settings depending on how they were set. If JVM_HEAPSIZE was set to 128, which is below the default of 256 for JVM_HEAPSIZE, and JVM_MINHEAPSIZE was not set (its default is also 256), then the resulting values used were both 256, which is not the expected result. The expected result would have been to set both values to 128. (MD13184) getRemoteInterfaceClass and getPrimaryKeyClass EJBMetaData methods may return the bean's HomeInterface class instead. The container's EJBMetaData implementation was erronously returning the EJB's HomeInterface class for the methods getRemoteInterfaceClass and getPrimaryKeyClass. This situation occurs when the RemoteInterface of PrimaryKey class is processed by the container's classloader because it can not be resolved via the caller's classloader. (MD13232) An uncaught throw of a long in session initialization can occur if a connection cannot be created. In getSessionHandle, if we have to create a new session object, there is try/catch logic to catch any longs thrown because of errors, and a -1 is returned to the caller. However, if a previously used session object is being reinitialized and a failure occurs, there is no try/catch to capture the error and convert it to a -1 return code. The long is thrown back into the caller, who is not expecting it. In a Control Region, this would surface as an unexpected exception caught by bbooboat's removeAndProcessWork method. ( PQ57023) Customers are seeing the "Class-Path:" entry within their EjbJar and/or War file's MANIFEST.MF file getting removed during System Management End User Interface (Administration and Operations applications), also known as the SM EUI, processing. Also, customers cannot deploy an EAR file through SM EUI during the EarFileProcessing step of the deploy processing if an EAR (application) requires references to external JAR/ZIP file during run time which causes NoClassDefFoundError during deploy. The "Class-Path:" entry within the MANIFEST.MF file of the J2EE Module was getting removed during SM EUI processing due to new J2EE v1.3 support that addresses the fact that "Class-Path:" entry was never added to WebSphere 390 J2EE archive handling code. In the meantime, new WebSphere Distributed releases added this support in their tooling, as well as in their run time, to allow new ClassLoading functionality that requires this new "Class-Path:" entry to be present. Also, before the Deployment processing step of SM EUI, we currently require our customers to specify their external JAR/ZIP in the SM server's CLASSPATH used by their application to avoid NoClassDefFoundError during the EarFileProcessing step of the deployment. Although allowing deployment of an application that requires external JAR/ZIP during run time is an optional feature even in the J2EE v1.3 specification, WebSphere 390 will support this function due to rising demand for this functionality from various customers.Problem conclusion APAR PQ59929 provides the following problem resolution: (MD13170) Tooltip support has been added to the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, which allows long values in the environment tables to be seen when not in modify mode. In addition, an Environment Viewing Dialog has been added that allows customers to view and copy values into the clipboard. This Environment Viewing Dialog opens with a double click on a name or value. or by pressing enter when a name or value has the focus. (MD11484) Calls have been added on thread exit to detach from the JVM, and when the main thread ends, to destroy the JVM. (MD12385) The generic catch blocks in readEarFile and readComponents were modified to include the original exception information in message BBON1201, which enables it to be seen by the user in the SM EUI message log. (MD12846) Support has been modified such that the container now properly converts minor codes in the form of strings into the integer format CORBA system exceptions use. (MD12977) Support was added to bbossmet.plx to obtain the pointer to the ACEE structure for the current thread in the following manner: 1) RRS, or if not in the RRS then 2) TCB, or if not in the TCB then 3) ASXB (MD13101) Support has been added to assign names to caches which use the default. The name of the cache will be partly based on the security principal and credentials specified by the application. In this way, applications using a different naming principal and different credentials will use different caches by default. (MD13182) The parser code for the JVM_HEAPSIZE and JVM_MINHEAPSIZE environment variables was rewritten to yield more predictable results. (MD13184) getRemoteInterfaceClass and getPrimaryKeyClass EJBMetaData methods have been modified to properly look up the correct class instance when using the container's classloader. (MD13232) Support has been modified to add the same try/catch logic that is around the creation of a new session, around the reinitialization of an existing session. ( PQ57023) In the SM EUI Reference and Resource Resolution Dialog, it is now possible to specify the "Class-Path:" entry of J2EE Module's MANIFEST.MF. If the application contains a Wrapper EjbJar (e.g. WAR == myServlet.war --> Wrapper EjbJar == myServlet_WebApp.jar) for a War file, the "Class-Path:" value is read out of the War file and written into both the Wrapper EjbJar file and the War file for synchronization of the two. Otherwise, regular EjbJar file's "Class-Path:" entry will be modified directly. With this support, deploying an application (EAR) which refers to classes packaged outside the application will not require SM's CLASSPATH to be modified in order to successfully deploy without potential NoClassDefFoundError EarFileProcessing exception. The following publication was revised as a result of APAR PQ59929: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-04 ________________________________________________________________ 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 14, pg. 397 (new message) C9C2126E Explanation: The destroyJavaEnv external function was not found in the BBOLRT dll. User Response: Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA. C9C2126F Explanation: The detachThreadFromJVM external function was not found in the BBOLRT dll. User Response: Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA. C9C21270 Explanation: The BBOLRT dll was not able to be loaded. User Response: Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA. APAR PQ59929 is associated with SERVICE LEVEL W401046 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: UQ65454 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 #: PQ59929
IBM Group: Software Group
Modified date: Jul 15, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.