APAR status
Closed as program error.
Error description
During a getConnection request it is possible that a connection could get a Stale Connention Exception and be returned to the free pool for reuse. This will cause an application to be trapped in a cycle where it is unable to get a connection even after the cause of the stale connection is addressed. This only happens if the stale Connection Exception happens during an allocate connection request. [7/23/08 14:11:02:837 CEST] 00000035 GenericDataSt > mapExceptionHelper Entry [7/23/08 14:11:02:837 CEST] 00000035 DB2DataStoreH > findMappingClass for: com.ibm.db2.jcc.c.DisconnectException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Connection reset. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: GA4B4F28.O125.080723120940 Entry [7/23/08 14:11:02:837 CEST] 00000035 DB2DataStoreH 1 the DataStoreHelper is: OreDataStoreHelper@438f12c3 [7/23/08 14:11:02:837 CEST] 00000035 DB2DataStoreH < findMappingClass: return Exit class com.ibm.websphere.ce.cm.StaleConnectionException 7/23/08 14:11:02:838 CEST] 00000035 GenericDataSt < mapExceptionHelper: Mapping was done returning: Exit com.ibm.db2.jcc.c.DisconnectException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Connection reset. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: GA4B4F28.O125.080723120940 at com.ibm.db2.jcc.a.a.a(a.java:378) at com.ibm.db2.jcc.a.hb.b(hb.java:191) at com.ibm.db2.jcc.a.hb.c(hb.java:238) at com.ibm.db2.jcc.a.hb.c(hb.java:353) at com.ibm.db2.jcc.a.hb.v(hb.java:1364) at com.ibm.db2.jcc.a.mb.b(mb.java:153) at com.ibm.db2.jcc.a.c.tb(c.java:319) at com.ibm.db2.jcc.c.j.l(j.java:368) at com.ibm.db2.jcc.a.a.l(a.java:526) at com.ibm.db2.jcc.c.j.c(j.java:235) at com.ibm.db2.jcc.c.jg.d(jg.java:2284) at com.ibm.db2.jcc.c.jg.ab(jg.java:1360) at com.ibm.db2.jcc.c.jg.execute(jg.java:1344) at XXXXXXXXXXXXXXXXXXXXX.doConnectionSetupPerGetConnection(XXXXXXX XXXXXXX.java:48) at XXXXXXXXXXXXXXXXXX.doConnectionSetupPerGetConnection(XXXXXXXXXX. java:35) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.getConnectio n(WSRdbM anagedConnectionImpl.java:2715) at com.ibm.ejs.j2c.MCWrapper.getConnection(MCWrapper.java:1776) at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionM anager.j ava:627) at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD ataSourc e.java:414) at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD ataSourc e.java:382) at StalderDBServlet.doGet(StalderDBServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.servic
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.0.2 who use the IBM RRA (relational * * resource adapter). * **************************************************************** * PROBLEM DESCRIPTION: A getConnection request could get a * * Stale Connention Exception and be * * returned to the free pool for reuse. * **************************************************************** * RECOMMENDATION: * **************************************************************** During a getConnection request it is possible that a connection could get a Stale Connention Exception and be returned to the free pool for reuse. This will cause an application to be trapped in a cycle where it is unable to get a connection even after the cause of the stale connection is addressed. This only happens if the stale Connection Exception happens during an allocate connection request. [7/23/08 14:11:02:837 CEST] 00000035 GenericDataSt > mapExceptionHelper Entry [7/23/08 14:11:02:837 CEST] 00000035 DB2DataStoreH > findMappingClass for: com.ibm.db2.jcc.c.DisconnectException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Connection reset. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: GA4B4F28.O125.080723120940 Entry [7/23/08 14:11:02:837 CEST] 00000035 DB2DataStoreH 1 th
Problem conclusion
The problem was fixed and only occurs on V6.0.2 The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.33 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
PK69496
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-23
Closed date
2008-09-10
Last modified date
2008-09-10
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
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022