Protocol Specific Error Codess Tcp/ip Sockets Db2connectioncorrelator
for Linux, Unix, and Windows Forum > Topic: HELP! Error trying to connect to DB2.This topic has been locked. 6 replies Latest Post - 2005-09-11T17:59:12Z by SystemAdmin Display:ConversationsBy Date 1-7 of 7 Previous Next SystemAdmin 110000D4XK 17917 Posts Pinned topic HELP! Error trying to connect to DB2. 2005-07-11T17:06:31Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. Hi! I get this error when i try to connect to my database: com.ibm.db2.jcc.b.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 at com.ibm.db2.jcc.a.a.a(a.java:428) at com.ibm.db2.jcc.a.ab.b(ab.java:175) at com.ibm.db2.jcc.a.ab.c(ab.java:222) at com.ibm.db2.jcc.a.ab.c(ab.java:337) at com.ibm.db2.jcc.a.ab.v(ab.java:1447) at com.ibm.db2.jcc.a.bb.a(bb.java:39) at com.ibm.db2.jcc.a.b.e(b.java:1232) at com.ibm.db2.jcc.a.b.b(b.java:1147) at com.ibm.db2.jcc.a.b.q(b.java:931) at com.ibm.db2.jcc.a.b.a(b.java:702) at com.ibm.db2.jcc.a.b.
are available V6.0.2: Java SDK 1.4.2 SR13 Cumulative Fix for IBM WebSphere Application Server V6.0.2: Java SDK 1.4.2 SR12 Cumulative Fix for IBM WebSphere Application Server 6.0.2.37:Java SDK 1.4.2 SR13 Cumulative Fix for IBM WebSphere Application Server 6.0.2.39:Java SDK 1.4.2 SR13 FP2 Cumulative Fix for WebSphere Application Server 6.0.2.41:Java SDK 1.4.2 SR13 FP4 Cumulative Fix for WebSphere Application Server 6.0.2.43:Java SDK 1.4.2 SR13 FP5 Cumulative Fix for WebSphere Application Server Subscribe You can track all active https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=86244 APARs for this component. 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 http://www-01.ibm.com/support/docview.wss?uid=swg1PK69496 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
JDBC Connection Pool Timeout Errors posted by SpringSource on February 9, 2010 12:44 PM If the http://www.tomcatexpert.com/knowledge-base/jdbc-connection-pool-timeout-errors database server times out a connection, the connection pool on Tomcat side would not be aware of its disconnection. If the database server times https://forum.hibernate.org/viewtopic.php?f=1&t=1030928&view=next out a connection, the connection pool on Tomcat side would not be aware of its disconnection, and could throw thefollowing exception in Tomcat: Caused protocol specific by: 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: Read timed out. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: CCD3560A.K404.080507130918 at com.ibm.db2.jcc.b.a.a(a.java:373) at com.ibm.db2.jcc.b.gb.b(gb.java:191) at com.ibm.db2.jcc.b.gb.c(gb.java:238) at com.ibm.db2.jcc.b.gb.c(gb.java:353) protocol specific error at com.ibm.db2.jcc.b.gb.v(gb.java:1362) In order to prevent the exception, the connection pool can validate the connection. In doing so, two attributes can be added to the JDBC resource, testOnBorrow and validationQuery respectively: name="jdbc/dsSos" auth="Container" type="javax.sql.DataSource" username="******" password="*******" driverClassName="com.ibm.db2.jcc.DB2Driver" factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" maxIdle="2" maxWait="10000" url="jdbc:db2://mydbURL:50000/MYDB" maxActive="15" removeAbandoned="true" removeAbandonedTimeout="300" testOnBorrow="true" validationQuery="some sql..." logAbandoned="true" "some sql..." In the above example should be a valid SQL query that the connection pool will execute to ensure a live connection is returned to the application. The embedded query should be simple and efficient. For example: For Oracle: validationQuery="select 1 from dual" For MySQL:validationQuery="select 1" For more than 10 years, SpringSource employees have been supporting Apache technologies, with unparalleled experience and commitment to the Apache Software Foundation. More than 400 of the Fortune 500 count on SpringSource to support their mission-critical business applications. Leaders of the Apache Software Foundation, including Board Members, wor
Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.