Here is a thought, and PLEASE to all of you gurus out there, feel free to
criticize / slam it!!!
Create a class which handles the database connections. Instantiate that class
at "user logon" (whatever that would represent in your environment), and add the
instantiation to the session object. Now, each servlet can access the object.
I'm planning on doing this for a side project I am working on, does it make
sense?
Thanks,
Jean
Jarec Basham wrote:
> Hi all,
>
> I've just inherited a servlet based system that makes a great use of an
> Oracle database. To be more precise every servlet inherits a base servlet
> which opens a database connection at the start of the servlets run and
> closes it when the run finished. This looks to me like a real system killer
> as load increases and I am currently looking at solutions to implement
> connection pooling.
>
> What I need to try to find out in the short term is how many connections
> Oracle can handle before it chokes on the load and what sort of magnitude of
> performance degradation we are likely to see as we approach this figure. If
> anyone has any experience of this kind of issue any input would be greatly
> appreciated.
>
> Thanks in advance
>
> Jarec
>
> ___________________________________________________________________________
> 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
