>>> "Alvin, lau" <[EMAIL PROTECTED]> 4/17/99 2:18:07 PM >>>
>re: it's will raise another problem when there is a connection never
return to the pool! What should I do????
The problem is related only to servlets that are unloaded (why do you
say uploaded?) automatically.
As far as I know all engines only do this with servlets loaded from
the /servlets directory.
So the first solution (and the one I prefer) is to use a path-bound
servlet loaded in your engine at run time.
Alternately, if this is not possible, you could try putting a
refernce to the pool into an attribute. As long as the attribute
exists (thus keeping the reference from the GC) the pool will
continue.
If this is not possible (and it isn't with version 2.0 of the API)
then wither upgrade your engine to one that supports version 2.1 or
use a session hat never invalidates to hold a reference to the pool.
Essentially all you need to do is keep the pool persistent by making
sure there is some persistent reference. You could create a
daemonThread that never gets destroyed and I'm sure there must be
plenty of other ways.
Really the problem in this detail only exists with version 2.0 and
even then only with /servlets Servlets. Get a version 2.1 engine or
use a bound path is my conclusion.
Nic Ferrier
Tapsell-Ferrier Ltd
www.tapsellferrier.co.uk
___________________________________________________________________________
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
