PQ81582: 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 PQ81582 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ81582 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD17708) When federating a node into a Deployment Manager an exception. The exception is: WSVR0314E: Failed to parse /WebSphere/V5R0M0/AppServer/config /cells/PLEX1Network/variables.xml at line -1, column -1 org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.util.ErrorHandlerWrapper. createSAXParseException(ErrorHandlerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper. fatalError(ErrorHandlerWrapper.java:213) at org.apache.xerces.impl.XMLErrorReporter. reportError(XMLErrorReporter.java:366) at org.apache.xerces.impl.XMLErrorReporter. reportError(XMLErrorReporter.java:296) at org.apache.xerces.impl.XMLScanner. reportFatalError(XMLScanner.java:1244) In some cases the config/ repository is deleted and must be preserved from backup. When the logs where investigated the error was: WSVR0314E: Failed to parse /WebSphere/V5R0M0/AppServer/ config/cells/PLEX1Network/variables.xml at line -1, column -1 Or something similar a failure to parse variables.xml. The cause of this is the cell name of the base server, is the same as the cell name of the DeploymentManager that the addNode was performed against. This is not allowed. A more useful message must be sent and addNode terminated gracefully and the repository untouched. (MD18389) The ability to override the standard XSL files by picking new versions up from the classes directory. Since the properties/xsl directory is a symlink to /usr/lpp, we need a way to override the XSL files much like we do with classes in the classes directory. (MD18736) The Update Runtime button on the webservices security panels fails to do what is expected. Information has been changed in the TrustAnchor window under: Servers->Application Servers->server1-> Web Services:Default bindings for Web Services Security The changes were saved and then went to TrustAnchor panel and selected Update Runtime button. The button is supposed to allow changes to be dynimically updated in runtime without having to restart AppServer. The problem is due to the absence of the mbean in the control region. The WebServicesSecurityAdmin.xml, indicates that the Mbean is running in the control process, but instead is running in the servant. (MD18792) During the parsing of an XML document (e.g. by a SOAP server), a list of attributes is compiled for each parsed element. This is typically done by the underlying XML parsing facility (the XML parser). Apparently, the time it takes the XML parser to compile the list of attributes (in a given XML element) is quadratic in the size of the list. That is, an XML element containing N attributes incurs a processing time proportional to N*N. (MD18926) org.omg.CosNaming.NamingContextPackage.NotFound in Network Deployment configuration because corbaloc URL is incorrectly resolved to the Node Agent. (MD18960) In the administrative console, on the Trust Association page (navigate to Security -> Authentication Mechanisms -> LTPA -> Trust Association), clicking either OK or Cancel returns a blank page. (MD19041) Administration console helps files need to be updated. (MD19084) In the Administrative Console, the local OS type is incorrectly shown as SAS rather than SAF. On the Local OS User Registry panel (Security > User Registries > Local OS), the value in the Local OS Type field should be "SAF" and not "SAS". iption should refer to the System Authorization Facility (SAF) rather than SAS. (MD19115) ORB Threadpool active thread count is always zero. PMI ORB Threadpool module activeThreads field is always zero. Tivoli Performance Viewer and Tivoli ITMP both consistently report only a zero value for ORB threadpool active threads - even when monitoring is occurring when work is dispatched and threads are clearly active. For example while monitoring long running requests. Active thread count is zero because code is missing. (MD19132) Need to ship runtime component of WSADIE performance enhancement fixes for applications developed with WSADIE tooling which use JCA Connection Factories. This corresponds to WebSphere Distributed APAR PQ82123. Also, problem deploying processes developed in WSADIE containing services with "reasonably complex" COBOL or C types, causing the abend. This corresponds to WebSphere Distributed APAR PQ82999. Without the runtime component of the WSADIE performance fixes, applications developed at a level of WSADIE 5.1 containing the tooling component of the performance fixes will fail when run on WebSphere Application Server V5.0 for z/OS. Exceptions such as the following two may be seen in such a case: - java.lang.NoClassDefFoundError: org/apache/wsif/providers/jca/ WSIFProviderJCAExtensions2 - javax.resource.spi.IllegalStateException: CTG9617E: ECI connection closed. With the runtime fix in WAS z/OS, users can run applications developed at a level of WSADIE not containing the tooling portion of the performance fix, in which case they will run fine but without the performance fix. Or they can run applications developed in a level of WSADIE containing the performance fix, in which case they will get the full benefit of the performance fix. The details of the 2nd problem, (WAS Distributed APAR PQ82999) are that WSADDeployAndInstallService.generateDeploymentCodeFor ProcessModule() can cause the JVM to abend. (MD19139) Reauthentication opportunities missed (for JCA connectors which support reauthentication). New ManagedConnections created instead of using exisiting, pooled ManagedConnections (for JCA connectors which support reauthentication).Problem conclusion APAR PQ81582 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD17708) Code was added to check the cell names before proceeding with addNode. Also the following message was added: ADMU0184E=ADMU0184E: Duplicate Entry Exception: An exception occured while checking the DeploymentManagers cell name: {0} The cell name for the Base Server must not match that of the DeploymentManager (MD18389) Logic of the buildTranslets() method of the Config2NativeTransformerXalan class was changed as follows: 1. Check for the existance of xsl files in the override (classes) directory? 2. If none exist, set the local variable xsl_loc as is currently done, i.e., to the path of the "standard" directory, WAS_INSTALL_DIR/properties/xsl. 3. If at least one override xsl file exists, do as follows: A. Create a new temporary directory - WAS_INSTALL_DIR/wstemp/XSLtemp B. Copy all xsl files from the "standard" directory to the new directory C. Copy all xsl files from the override directory to the new directory (this will cause any new xsl files to overwrite their standard versions.) D. Set the local variable xsl_loc to the path of the new directory. 4. Build each template and "put" them into the templates HashMap as is currently done, i.e., based on the setting of xsl_loc. (MD18736) Modified the xml file to indicate that the Mbean is running in the servant region. (MD18792) B2B xml parser has been updated with this performance degradation addressed. (MD18926) The corbaloc URLs in the Node Agent are sometimes resolved to the Node Agent because the key is missidentfied as a object key. Code was updated to correctly identify the keys as remote. (MD18960) An error in the struts-config.xml file was causing an undefined page to be used. The file was corrected. (MD19041) Administration console helps files have been updated. (MD19084) The default local OS type and the field description were modified to refer to SAF. (MD19115) Support was added to record thread activity. (MD19132) Fixes for WebSphere Application Server Distributed APARs PQ82123 nad PQ82999 have been shipped in the WebSphere Application Server V5.0 for z/OS. (MD19139) Fix made to matching algorithm to allow for greater reuse of ManagedConnections via reauthentication (for JCA connectors which support re-authentication). APAR PQ81582 is associated with SERVICE LEVEL W502002 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: UQ85128 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ81582.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 #: PQ81582
IBM Group: Software Group
Modified date: Mar 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.