db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-574) Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement which represents a shared plan.
Date Fri, 16 Sep 2005 18:51:54 GMT
Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement
which represents a shared plan.
-------------------------------------------------------------------------------------------------------------------------------

         Key: DERBY-574
         URL: http://issues.apache.org/jira/browse/DERBY-574
     Project: Derby
        Type: Bug
  Components: SQL, JDBC  
    Versions: 10.2.0.0    
    Reporter: Daniel John Debrunner
     Fix For: 10.2.0.0


The timeout is being set on the class GenericPreparedStatement, but this
represents a statement plan and can be shared across multiple
connections (through the statement cache). Thus if two connections
execute the same statement with different timeouts, they will interfere
with each other with the timeout values.

I think the solution is to pass the timeout into the execute method of
org.apache.derby.iapi.sql.PreparedStatement, not store it as a field in
GenericPreparedStatement.

[from http://mail-archives.apache.org/mod_mbox/db-derby-dev/200509.mbox/%3c4322251C.6040700@debrunners.com%3e
]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message