db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: [jira] Updated: (DERBY-210) Network Server will leak prepared statements if not explicitly closed by the user until the connection is closed
Date Wed, 01 Feb 2006 16:47:50 GMT
> In other words, the patch seems to provide significant improvement to Derby robustness
with regards to cases where statements are not always explicitly closed by the application
using the Derby client. The garbage collector is able to collect much more garbage with the
patch than without.

This is *excellent* news!

Can you tell, at this point, whether there is a secondary leak
that we must additionally pursue? That is, does it seem as though,
if we are able to incorporate the DERBY-210 fixes into the base
product, we will be able to run DOTS without memory exhaustion errors?

I guess what I'm asking is: what duration of test, with the patch
applied, would be enough to satisfy us that there are no additional
memory leaks exposed by this test?



View raw message