Fixes are available
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
A database connection leak problem can occur in WebSphere Application Server when used with a WebSphere Portal Server which includes the Spring Framework. The problem only occurs when PMI Request Metrics is enabled. The leak occurs because a suspended LTC holding a shareable database connection never gets cleaned up due to the following exception: [7/22/09 15:33:54:221 EDT] 000000d2 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Servlet. Exception thrown : org.springframework.web.util.NestedServletException: View rendering failed; nested exception is java.lang.RuntimeException: SRV.8.2: ResponseWrapper objects must extend either ServletResponseWrapper or HttpServletResponseWrapper at org.springframework.web.servlet.Servlet.processReque st(Servlet.java:93) at org.springframework.web.servlet.Servlet.doGet(Servlet.java :65) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWr apper.java:282) at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java :459) at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java: 265) at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.j ava:262) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1096) The connection leak logic data from a showPoolContents output or a ConnLeakLogic=all trace will show that LTCs are suspended, Handle counts are 0, and Times inuse are long: com.ibm.ws.LocalTransaction.LocalTranCoordImpl@72a0a0cf;SUSPENDE D; MCWrapper id 3a781488 Managed connection WSRdbManagedConnectionImpl@218c0ab5 State:STATE_TRAN_WRAPPER_INUSE Thread Id: 0000056e Thread Name: WebContainer : 1012 Handle count 0 Start time inuse Thu Jul 23 04:00:20 EDT 2009 Time inuse 675 (seconds) com.ibm.ws.LocalTransaction.LocalTranCoordImpl@52308e3c;SUSPENDE D; MCWrapper id 4ce842e9 Managed connection WSRdbManagedConnectionImpl@2c80d19a State:STATE_TRAN_WRAPPER_INUSE Thread Id: 0000037d Thread Name: WebContainer : 593 Handle count 0 Start time inuse Thu Jul 23 02:13:22 EDT 2009 Time inuse 7094 (seconds) com.ibm.ws.LocalTransaction.LocalTranCoordImpl@55f91137;SUSPENDE D; MCWrapper id 2e199aba Managed connection WSRdbManagedConnectionImpl@12fd40fb State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000446 Thread Name: WebContainer : 758 Handle count 0 Start time inuse Thu Jul 23 03:13:28 EDT 2009 Time inuse 3488 (seconds)
Local fix
Disable PMI Request Metrics.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 6.1 users * **************************************************************** * PROBLEM DESCRIPTION: System hangs because the database * * connection are exhausted. * **************************************************************** * RECOMMENDATION: * **************************************************************** After serving a request, the WebContainer tries to release all the suspended local transaction containment (LTC) which in turn releases the database connections to a pool so that they can be reused in the subsequent requests. When PMI Request Metrics is used and the response object is not wrapped correctly, the following exception may be seen in the log: ServletWrappe E SRVE0068E:Uncaught exception thrown in one of the service methods of the servlet: Servlet. Exception thrown : java.lang.RuntimeException: SRV.8.2: ResponseWrapper objects must extend either ServletResponseWrapper or HttpServletResponseWrapper The Webcontainer does not handle the exception correctly and does not invoke the suspended LTC. As a result, the database connection is not released to the pool. These accumulate over time, and eventually all of the available connections are depleted.
Problem conclusion
The WebContainer code was modified to handle the exception properly and invoke the suspended LTC to release the database connections. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.29. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK92140
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-23
Closed date
2009-08-25
Last modified date
2009-08-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
28 December 2021