[ http://issues.apache.org/jira/browse/DERBY-941?page=comments#action_12374937 ]
V.Narayanan commented on DERBY-941: ----------------------------------- Hi, We are throwing the error occurred event only upon doing an execute on the PreparedStatement. If the ConnectionPoolManager did know that the temporary table or the table used in the PreparedStatement or in the generalized case knew of a DDL invalidating a PreparedStatement why would it do a execute on the PreparedStatement? Does'nt this qualify as a faulty Pooling implementation? If it were using a temporary table it would do an execute only during the time that the temporary table exists. Narayanan > Add JDBC4 support for Statement Events > -------------------------------------- > > Key: DERBY-941 > URL: http://issues.apache.org/jira/browse/DERBY-941 > Project: Derby > Type: New Feature > Components: JDBC > Versions: 10.0.2.0 > Reporter: Rick Hillegas > Assignee: V.Narayanan > Attachments: ListenerTest.java, statementeventlisteners_embedded.diff, > statementeventlisteners_embedded.stat, > statementeventlisteners_embedded_v2.diff, > statementeventlisteners_embedded_v2.stat, > statementeventlisteners_embedded_ver1.html > > As described in the JDBC 4 spec, sections 11.2, 11.7, and 3.1. > These are the methods which let app servers listen for connection and > statement closure and invalidation events. > Section 11.2 of the JDBC 4 spec explains connection events: Connection pool > managers which implement the ConnectionEventListener interface can register > themselves to listen for "connectionClosed" and fatal > "connectionErrorOccurred" events. App servers can use these events to help > them manage the recycling of connections back to the connection pool. > Section 11.7 of the JDBC 4 spec explains statement events: Statement pools > which implement StatementEventListener can register themselves to listen for > "statementClosed" and "statementErrorOccurred" events. Again, this helps > statement pools manage the recycling of statements back to the pool. -- 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
