Let me clarify some more...

I am using connection pooling and each connection "commits" after a user is done with a session, but the DB connection remains open and ready for the next user.


----- Original Message ----
From: slalom91 <slalom91@...>
To: firebird-support@yahoogroups.com
Sent: Saturday, June 9, 2007 11:36:35 AM
Subject: [firebird-support] Idle Connection / Cache Release

Environment is as follows:

FB v2.0.1 (Classic)
Windows Server 2003
Dual Core Xeon

I am observing that FB connections seem to be releasing memory back to
windows after remaining idle for some time. I am basing these
assumptions on the amount of memory each process indicates is allocated
to it via Task Manager. I am wondering if this behavior is by design
and if it is configurable.

Thanks.




[Non-text portions of this message have been removed]