Re: Validation query

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Tom Moreau (tom_at_dont.spam.me.cips.ca)
Date: 05/12/04 

Date: Wed, 12 May 2004 18:56:52 -0400

>From what I see, you should just take the hit up front. IOW, when the DB
server gets restarted, you'll populate your connection pool and eventually
reach a steady state. If you want, you could put a process in place to kick
off a bunch of those validation queries when the DB server fires up and once
they've completed, the pool is open. (Pun intended.) 

-- 
   Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada
www.pinnaclepublishing.com/sql
.
"Bob Lee" <wliuei@hotmail.com> wrote in message
news:e8EpiIHOEHA.904@TK2MSFTNGP12.phx.gbl...
Tom,
The whole story:
We have a Web application. The application uses MS SQL
Server database and Apache Jakarta commons-dbcp
connection pool to communicate with the database.
Every time after the database is re-started, the
application server is forced to re-start. Otherwise,
the connections that the pool keeps become invalid and
the system cannot get a connection for the database.
I think there is a possible solution: add a
validationQuery on the connection pool and set the
testOnBorrw parameter to true. However, I am wondering
this could cause an overhead on the transaction. The performance is a
big issue on our application. How much will it affect the performance?
Bob
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Relevant Pages