Alvin-
One approach to growing/reducing your pool is to create a connection pool
monitor class. Have this thread "wake-up" every few milliseconds to check
the pool for active(in-use) connections. When the pool reaches a certain
threshold (available connections vs. in-use connections) add more
connections to the pool. Likewise, when the pool gets "bloated", remove
some connections from the pool.
I have some code (beta) that I wrote for our API that does this. Let me
know if you want any snippets.
John Kirby
DISC
-----Original Message-----
From: Alvin Lau [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 26, 1999 6:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Connection Pool
The first time i see connection pool is in john hunter's book, and that
pool doesn't reduce its size after a connection return. can you tell me
where i can donwload a better package? I don't want to write it by myself.
thank anyway,
alvin
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
