commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ori (JIRA)" <>
Subject [jira] Created: (DBCP-244) Connection socket hangs sporadically in DBCP 1.2.2 but not 1.2.1
Date Tue, 09 Oct 2007 22:26:50 GMT
Connection socket hangs sporadically in DBCP 1.2.2 but not 1.2.1

                 Key: DBCP-244
             Project: Commons Dbcp
          Issue Type: Bug
    Affects Versions: 1.2.2
         Environment: Fedora Core 3, MySQL 4.2.2. with the latest driver (5.07). Exceptions
only occur in the "job processing" JVM, which sits idle for long periods of time and occasionally
wakes up to interact with the database.
            Reporter: ori

I think I've traced an exception to DBCP's code.

Communication with the database is hanging sporadically in a production environment. If I
don't set the socketTimeout property on the underlying connection, it will hang forever. With
the socketTimeout property, I get the following exception:

com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

MESSAGE: Read timed out

STACKTRACE: Read timed out
       at Method)
       at com.mysql.jdbc.util.ReadAheadInputStream.fill(
       at com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(
       at com.mysql.jdbc.MysqlIO.readFully(
       at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(
       at com.mysql.jdbc.MysqlIO.checkErrorPacket(
       at com.mysql.jdbc.MysqlIO.sendCommand(
       at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
       at com.mysql.jdbc.Connection.execSQL(
       at com.mysql.jdbc.Statement.executeUpdate(
       at com.mysql.jdbc.Statement.executeUpdate(
       at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(

It always happens in an infrequently used JVM (not an app server handling frequent connections).
So it's likely the offending connection was asleep for a long time before the exception occurs.

I've confirmed that this issue only occurs using 1.2.2 and not 1.2.1. I've been looking through
the changelogs but can't find anything that would cause this behavior.

Does somebody familiar with the codebase have any idea what change (1.2.1->1.2.2) could
be causing this behavior? 


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message