Cammarano Richard wrote:
>
> i am currently using a connection pool manager that is designed as a
> singleton where I call ConnectionManager.getInstance() to return the
> single pool instance. At first I was storing the connection manager in
> the servlet context until my coworker pointed out that I didn't need to
> store it at all. The singleton pattern guarantees the single pool
> instance which can always be retrieved by
> ConnectionManager.getInstance() no matter where you are in the
> application (assuming you have imported the class in the JSP or
> servlet).
What stops the instance from getting garbage collected? I read that
starting version something-something-something, the garbage collector is
more aggressive and will collect instances of objects that are only
referred to by a member variable in the same class.
Sam
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
