[Proxool-developer] Possible bug with CallableStatment

[Neil M. <nm...@pr...>]

I'm not sure if the bug tracker on Sourceforge is used much, so I  
thought I'd post this here. We're getting a warnings in our logs when  
using CallableStatements (I added a stack trace for additional info):

Jan 10, 2007 3:17:59 PM org.logicalcobwebs.proxool.ProxyConnection  
registerClosedStatement
WARNING: 001210 (01/02/00) - #16 registered a statement as closed  
which wasn't known to be open.
java.lang.Exception: Trace
         at  
org.logicalcobwebs.proxool.ProxyConnection.registerClosedStatement 
(ProxyConnection.java:181)
         at org.logicalcobwebs.proxool.AbstractProxyStatement.close 
(AbstractProxyStatement.java:116)
         at org.logicalcobwebs.proxool.ProxyStatement.invoke 
(ProxyStatement.java:93)
         at org.logicalcobwebs.proxool.ProxyStatement.intercept 
(ProxyStatement.java:57)
         at oracle.jdbc.internal.OraclePreparedStatement$ 
$EnhancerByCGLIB$$3f1a29db.close(<generated>)
         [local code]

Our code looks like this (the connection has already be gotten from  
Proxool and is passed to this method):

     public void execute(Connection con, String callSQL, Parameter[]  
params)
         throws SQLException
     {
         CallableStatement call = null;
	        try {
             call = con.prepareCall(callSQL);

             [... add parameters to the statement ...]

             call.execute();

             [... read returned parameters ...]
         }
         finally {
             if (call != null) {
                 call.close(); <-- exception is thrown here.
             }
         }
     }

We're using Oracle 10g and the lastest JDBC drivers from oracle.  
Can't see why this should cause a warning.

-n