Re: Tomcat reload / classloader / connection pool

2003-12-02 Thread Christopher Schultz
Marcel, The problems with Tomcat occur upon reload of the web app. The classloader reloads the whole app and all my DB connections get opened again. This wouldn't cause much pain if the existing connections were garbage collected i.e. finalized. This doesn't happen and after a couple of reloads

RE: Tomcat reload / classloader / connection pool

2003-12-02 Thread Marcel Stor
Christopher Schultz wrote: Marcel, The problems with Tomcat occur upon reload of the web app. The classloader reloads the whole app and all my DB connections get opened again. This wouldn't cause much pain if the existing connections were garbage collected i.e. finalized. This doesn't

RE: Tomcat reload / classloader / connection pool

2003-12-02 Thread Justin Ruthenbeck
At 04:21 PM 12/2/2003, you wrote: Christopher Schultz wrote: First of all, why is this so? This is likely because of the way you use the singleton. When you have a singleton (I use quotes because it's probably not a real singleton otherwise we would not be having this discussion) the

RE: Tomcat reload / classloader / connection pool

2003-12-02 Thread Marcel Stor
Justin Ruthenbeck wrote: At 04:21 PM 12/2/2003, you wrote: Christopher Schultz wrote: First of all, why is this so? This is likely because of the way you use the singleton. When you have a singleton (I use quotes because it's probably not a real singleton otherwise we