your
> PreparedStatement objects? (ideally in a try/finally block to ensure
> that you don't forget to close them when exceptions are thrown). I
> could see how not closing PreparedStatements could easily lead to
> Enhydra keeping references to the PreparedStatements.
>
> th
it.
Thanks again.
John
John Cook wrote:
> Barry,
>
> I got OptimizeIt configured, and it looks like it is jdbc2/PreparedStatement
> which is not being garbage collected. All of my PreparedStatement s stay
> visible in Optimize it and the number of instances never decreases
uld
> submit such that we could reproduce the problem and fix it, or you could
> use a java memory profiler to track down what objects are being
> allocated and not released. I personally like OptimizeIt as it has
> helped me solve quite a few memory leak problems with java code.
>
>
