Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3F7A98DB.3060000@cyberspaceroad.com>
Date: Wed, 01 Oct 2003 11:05:31 +0200
From: Adam Hardy <ahardy.struts@cyberspaceroad.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030917
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Datasource connections not released when reloading context
References: <40E9E4B9BEE4D211B62200A0CC3E01B0030BA5E6@rqiexch.resortquest.com>
In-Reply-To: 
 <40E9E4B9BEE4D211B62200A0CC3E01B0030BA5E6@rqiexch.resortquest.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Matt,
you don't destroy them, you just close them.

if (!conn.isClosed()) conn.close();


On 09/30/2003 12:51 AM Matt Raible wrote:
> If I'm getting my database connections from a JNDI resource (configured in
> server.xml) how do I destroy these suckers.  Sample code would be great - or
> tell me to RTFM.
> 
> Matt
> 
> -----Original Message-----
> From: Phillip Qin [mailto:Phillip.Qin@shareowner.com]
> Sent: Monday, September 29, 2003 8:04 AM
> To: 'Tomcat Users List'
> Subject: RE: Datasource connections not released when reloading context 
> 
> 
> - to release your DB connections when your app is shutdown or reloaded:
> implement destroy method in your servlet class to close them.
> - to prevent connections getting exhausted, use evictor if your use commons
> pooling and dbcp.
> 
> -----Original Message-----
> From: Jose Alfonso Martinez [mailto:trilock@linuxcenter.com.mx] 
> Sent: September 27, 2003 7:31 PM
> To: tomcat-user@jakarta.apache.org
> Subject: Datasource connections not released when reloading context 
> 
> Hi guys,
> 
> Does any one know if there is a possibility of tomcat, for any reason, to
> reload a context without telling it to do so????
> 
> I am having a problem that after 2 or 3 days without reloading tomcat,
> pooled-connections from the datasource get exahusted.
> 
> The only case I have seen that the number of pooled-connections is
> incremented is when I reloaded my context. In this case, the reloaded
> context's datasource opened a new set of connections to work on (leaving the
> older connections opened and not releasing them until tomcat is shutdown).
> If the context gets reloaded over and over again, eventually connections
> with the DBMS will get exahusted...
> 
> Is that the expected behavior???? To leave conections open when reloading a
> context????
> 
> Would there be another posibility for pooled-connections to get exahusted,
> once they were set up and correctly running???
> 
> Thanks in advance
> 
> Jose
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> 

-- 
struts 1.1 + tomcat 5.0.12 + java 1.4.2
Linux 2.4.20 RH9


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org