You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/09/16 20:51:54 UTC
[jira] Created: (DERBY-574) Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement which represents a shared plan.
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
[jira] Closed: (DERBY-574) Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement which represents a shared plan.
Posted by "Oyvind Bakksjo (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-574?page=all ]
Oyvind Bakksjo closed DERBY-574:
--------------------------------
Fix Version: (was: 10.2.0.0)
Resolution: Duplicate
> 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: JDBC, SQL
> Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
>
> 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