Hi Don,
We messed up at our end and found it ourselves. It is fixed now.
You're right, it does work OK.
However, we did get the error that states that SQLServer has
reached max number of connections, even when the Servlet
initializes the pool for the first time (which will try to get some
number of connections).
But this problem also hasn't appeared all day today, although we can't
think of anything we changed in the code that would have mattered.
If there is anything we have to watch out for while using
a DB ConnectionPool in a Servlet, we would like to know that.
Thanks!
Rali Panchanatham
-----Original Message-----
From: Don Junio Edillor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, March 30, 2000 02:41 PM
Subject: connection pool
>hello there!
>i got your email regarding the connection pool.. its very useful.. it
>optimizes the processing with the database..
>
>your message is not that clear to me.. can you explain it again? coz we
>never encountered that problem..
>
>-donjunio-
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>
___________________________________________________________________________
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
