PK02465: SHIP INTERNAL DEFECT FIXES FOR SERVICE LEVEL W502031. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Ship internal defect fixes for Service Level W502031.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PK02465 addresses the following * * defects in WebSphere Application Server * * V5.0 for z/OS: * * * * (MD20731) startServer.sh timed-out * * before the server finished * * initialization. * * * * (MD20785) Cleanup associated with * * receiving a StaleStatementException * * can cause a * * java.lang.NullPointerException to * * occur later on. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PK02465 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD20731) The waitForTerminationWithTimeout method (WS390ProcessGlue.java) is invoked by the NodeAgent to monitor the progress of a started WebSphere Application server. In this case the time-out value of 0 was given. The expected behavior was that the waitForTerminationWithTimeout method would loop indefinitely monitoring a specific server. However, on z/OS this method capped the maximum wait time to 280 seconds. The server being monitored had not completed initialization within the 280 seconds and the waitForTerminationWithTimeout method returned to its caller. The NodeAgent subsequently returns without waiting for initialization to complete. (MD20785) During cleanup of a Local Transaction Containment (LTC), WebSphere will close JDBC Statements and ResultSets that were not closed by the application. If during one of these close operations WebSphere receives an SQLException from the underlying JDBC driver that is recognized by WebSphere to indicate a stale statement, certain cleanup behavior is initiated which eventually results in a NullPointerException being thrown. The exception, which can be seen in the joblog of the application servant region, will look similar to the following: J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@4ac15d5a from resource jdbc/MyDataSource. Caught exception: java.lang.NullPointerException at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection. dissociate(WSJdbcConnection.java:896) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl. dissociateHandles(WSRdbManagedConnectionImpl.java:2148) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl. cleanup(WSRdbManagedConnectionImpl.java:2271) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1184)Problem conclusion APAR PK02465 fixes the following defects in WebSphere Application Server V5.0 for z/OS. (MD20731) The waitForTerminationWithTimeout method has been updated to honor the 0 time-out value as a wait until the target server terminates. (MD20785) StaleStatementException cleanup behavior was incorrectly setting certain fields to null, and this has been corrected. APAR PK02465 is associated with SERVICE LEVEL W502031 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: UK04679 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK02465.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 #: PK02465
IBM Group: Software Group
Modified date: Jul 12, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.