Subject rs.getStatement
Author Ian A. Newby
Hi All,
I'm just trying the Type 4 driver for the first time
(congratulations everyone for all the hard work) to replace
interclient.

I've hit a snag: We have lots of code as follows:

Connection con = PoolManager.getConnection();
ResultSet rs = con.createStatement().execute("select * from
employee")
while (rs.next) {
...
}
rs.getStatement.close();
rs.close();

The rs.getStatment.close() line always errors saying the statement
is already closed. How do I know its already closed?

Is it to do with automatic transactions?

Are there any workarounds?

This is a bit of a stopper, as its quite a large application.

By the way the line was added to prevent a memory leak in the system
when the same transaction was being used over and over again.

Regards
Ian Newby