In my work with MS SQL Server, I had 5
minutes as the setting. Anything older and it got dumped. Worked pretty well
and was long enough to deal with slower times of the day and still provide
great performance.
From: Arnett, Matt
[mailto:Matt.Arnett@xxxxxxxxxx]
Sent: Thursday, April 14, 2005
7:38 AM
To: users@xxxxxxxxxx
Subject: [cinjug-users] JDBC
connection pool test settings
WebLogic has a setting available, called
“Seconds to trust an idle pool connection”. If configured to
do so, WebLogic will test a DB connection prior to giving it to an application
when the app requests it. This “trust” option can greatly
reduce the total time it takes for you app to make a SQL call (especially when
several hundred SQL calls are rapidly issued on different connections) so that the
connection does not have to be tested every single time an app requests it.
My question is, does anyone use this option and what values
work best for you? This is with MS-SQL Server 2000 and soon to be Oracle
10g.
How long can you expect a connection in a pool to be in good
working state before it goes bad and needs to be recreated?
Thanks,
-Matt
This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a named
addressee you are hereby notified that you are not authorized to read, print,
retain, copy or disseminate this communication without the consent of the
sender and that doing so is prohibited and may be unlawful. Please reply to the
message immediately by informing the sender that the message was misdirected.
After replying, please delete and otherwise erase it and any attachments from
your computer system. Your assistance in correcting this error is appreciated.