On 3 Nov 2003 at 13:46, Ian A. Newby wrote:

> We found a similar problem using pooled connections in Java, it
> turned out we wern't closing all the statement objects correctly,
> leading to massive memory loss.
>
> Try closing pooled connections occasionally to see if that fixes it,
> we close about once every 500 connection usages just to catch any
> problems we have missed. It is likely that your problem relates to
> database access components being created but not freed correctly.

I'd second that. All DSQL resources (that are typically used in those
access layers) are bound to connection, not to transaction like in many
other database systems. So when they're not properly released by
application itself, they are automatically released when connection is
closed. When connection persists for long time, you can observe a
cumulative effect on server memory consumption, especially on
applications that are under heavy load (like any typical web-based
application).

Best regards
Pavel Cisar (ICQ: 89017288)
http://www.ibphoenix.com
For all your upto date Firebird and
InterBase information