On 11/8/06, Arturo FM  wrote:
> > While its not elegant, (a) is just a few seconds
> > work. If your application
> > can stand that, why not?
> What happens if an user is using a connection in this
> just moment? Probably he/she loose his/her session :(

Not if the sessions are stored persistently.  At worst the user will
get an error screen if the server is killed in the middle of the
request.  A reload in the browser will restore things.  The only
problem is if a state-changing action has occurred before the server
died (e.g., an online purchase): the user may get a "you've already
done this" message or it may try to do it again, depending on how the
application was written.

It's also worth looking at your access log.  People tend to
overestimate their server load.  Even with a hundred users logged in,
they'd have to be clicking things pretty fast to translate to several
requests per second (not counting images/stylesheets).  I used to work
at a popular magazine and we did extreme load testing on a new version
of our web site, only to discover the actual load was more like three
requests per minute.  Meaning the chance of somebody doing a request
at the moment you restart the server was not zero but it wasn't that
high either.

The pool would not recycle a connection while it's in use.  When it's
in use it's not in the pool.

You don't have to get a connection for each query.  Get one at the
beginning of the request and return it at the end.

--
Mike Orr