PQ77962: 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 PQ77962 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ77962 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD17365) An exception would occur when using wsadmin.sh install interactive mode. Example command: $AdminApp installInteractive <app> An exception of type: ava.util.zip.ZipException: EDC5111I Permission denied. (errno2=0x5B4C0002) was found. The problem was caused by an permissions error, where the wsadmin command would try to write temporary files to a place where it did not have right to. (MD17408) Browsing the server for an application archive file to install fails via the administrative console. Browsing the server for a resource adapter file to install also fails. There is also a missing link in the resource adapter installation path. This is a problem with application ear installation as well as resource adapter installation when the corresponding archive files are chosen from the server as opposed to the local machine where the browser runs. On the "Preparing for application installation" administrative console page, if the "Server path" is chosen and a node is browsed for the application ear file, when the browse process returns, the "Server path" field contains the following string "null<earfile.ear>". Similar behaviour is seen on browsing the node HFS for a resource adapter archive file via the "Install RAR" administrative console page. This is because the location to where the archive files are uploaded cannot be determined correctly. Also, the browse process on the "Install RAR" path, on choosing an archive file, returns to a blank page, instead of the page indicating the chosen archive file. (MD17428) When PMI is enabled, the PMI module ORB.thread.pool is not reporting any statistics. It should be reporting the same type of statistics consistent with what was provided in WebSphere Application Server version 4.0.1 for z/OS and OS/390. (MD17439) A new panel needs to be added to the administrative console. Add a new link "z/OS Location Service" under the "System Administration" category in the navigation tree. A click on the link leads to a new "Location Service Daemon" panel to config the location service daemon. (MD17455) Use of SQLJ by BMP beans or EJBs using DB2 JDBC to access a DB2 database will fail with "java.lang.RuntimeException: DB2SQLJConnectedProfile Received Error in Method Constructor: Unable to resolve the DB2SQLJConnection". WebSphere V5.0 for z/OS support for the DB2 390 Local JDBC Provider does not properly support the use of SQLJ. (MD17456) The following java parameter is needed in the shell scripts: -Djava.security=<location of updated java.security file> If not exceptions such as this occur: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service is not available. at com.ibm.ws.scripting.AbstractShell .setAndThrowScriptingException( AbstractShell.java:1175) The problem is missing JVM arguements, the problem was then broadened to include any shell script that might be missing arguements, the variable: $JVM_EXTRA_CMD_ARGS was added to the shell scripts that call java to fix this problem and the facilitate fixing later ones should the need arise. (MD17479) Transaction service does not resolve stale XIDs given to XAResources during controller restart. When an XAResource is involved in a global transaction, the transaction manager gives it a unique XID describing that resource's branch of the transaction. When the transaction is complete, the XID is deleted from the resource manager. Under certain conditions, such as resource manager failure, some of these XIDs may remain in the resource manager's log even after the transaction has completed. When the transaction service restarts with the resource manager, these XIDs are resolved and the branches of the transactions that the XIDs represent are either committed or rolled back, depending on the overall outcome of the transaction. The transaction service recieves all the XIDs that the resource manager knows about during recovery. It is the transaction manager's responsibility to filter out those XIDs that do not belong to it, and resolve the ones that do. The filter as implemented in the transaction manager is incorrect, and under certain conditions, all XIDs are filtered out whether the server owns them or not. This only happens when a controller has failed and is restarted. Servant failure filters the XIDs correctly.Problem conclusion APAR PQ77962 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD17365) Support was modified to set the java.io.tmpdir equals to the property com.ibm.ws.scripting.tempdir in wsadmin.properties. (MD17408) Code was added to obtain the appropriate path to which the application/resource adapter archive files were uploaded to. Also the missing link was identified and fixed, so that the browse process while installing a resource adapter archive can return to the correct location. (MD17428) Support has been added for PMI module ORB.thread.pool statistics. (MD17439) Support modified to add the new link "z/OS Location Service" under the "System Administration" category in the navigation tree. The new link will lead to a new "Location Service Daemon" panel which allows the configuration for 5 required fields: jobName, hostname, port, sslPort, and sslSettings. (MD17455) WebSpere for z/OS DB2 390 Local JDBC Provider support has been changed to correctly allow the use of SQLJ by BMP beans and EJBs using DB2 jdbc to access a DB2 database. (MD17456) The following parameter: $JVM_EXTRA_CMD_ARGS was set in the shell scripts, the value of the variable will be set in setupCmdLine.sh. (MD17479) Filtering code was modified to allow XIDs to be recovered when a controller fails and is restarted. APAR PQ77962 is associated with SERVICE LEVEL W500104 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: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ77962.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 #: PQ77962
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.