Re: The performance problem of server side PreparedStatement?

[Mark Matthews]

The JDBC spec doesn't let the driver implicitly cache the creation of a prepared statement, as most implementations (including ours) have prepared statements tied to a particular connection, even inside the server. Therefore when you close the connection, they go away.

If you want this functionality, you should use a connection pool that caches prepared statements. Most application servers offer this, as well as third-party connection pools (I happen to like c3p0, from http://c3p0.sourceforge.net/)

-Mark