Problems Caching and reusing JDBC CallableStatement objects

I have written an application that runs on the AS/400 and calls stored 
procedures using JDBC driver com.ibm.db2.jdbc.app.DB2Driver. My first release 
of the application created a new CallableStatement object each time I called a 
stored procedure. This has been working fine for some time now.

In an attempt to improve performance, I modified the application to cache the 
CallableStatement objects for each different stored procedure call, then 
reusing the CallableStatement object for subsequent stored procedure calls.  I 
am now getting the error *Conversion error on input host variable or parameter 
*N.* I returned to creating the new CallableStatement for every stored 
procedure call and the application works fine again. Caching the 
CallableStatements works fine against an Oracle database and improved 
performance by almost 10 percent.

Has anyone seen this problem before?  We are running V4R4 and JDK 1.1.7.

Thanks,

Al Heitkamp
H.B. Fuller Company
Arden Hills, MN



+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---