Carsten,

> I've done some more tests with Jaybird 1.5.2, but the problem with
> statement pooling still exists.
> My profiler says that most of memory growing are Strings and char[]
> and org.firebirdsql.gds.XSQLVAR and
> org.firebirdsql.jdbc.FBPrepredStatement and
> org.firebirdsql.jdbc.field.FBDateField and HashMap$Entry[] and
> LinkedList$Entry Objects. Most of these objects are created within
> the driver and are not released after the connection is released.

Do you have a standalone test case that you use to reproduce the issue? Can
you send it to me?

There was a bug with the pool when PreparedStatement.close() did not enforce
ResultSet.close(), but I have fixed this.

Roman