tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phillip Qin <Phillip....@shareowner.com>
Subject RE: Datasource connections not released when reloading context
Date Wed, 01 Oct 2003 18:00:44 GMT
There are two connections, one is between apache and db server's 1521 port
for login/authentication, the other is the real port that transmitting data.
Apply commons-dbcp and pool 1.1-RC1 to your common/lib and use evictor.

-----Original Message-----
From: Matt Raible [mailto:MRaible@RESORTQUEST.com] 
Sent: October 1, 2003 12:38 PM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context

I already do this, but when I "reload" my context, I get two database
connections, rather than one.  So each time I reload, I get an additional
connection - eventually resulting in an OutOfMemory Error (which I'm
attributing to this) after I reload 10-20 times.

Matt

-----Original Message-----
From: Adam Hardy [mailto:ahardy.struts@cyberspaceroad.com]
Sent: Wednesday, October 01, 2003 3:20 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context


actually that doesn't really close them, since it's a connection pool, 
but it tells the connection pool that they're free for someone else.

On 10/01/2003 11:05 AM Adam Hardy wrote:
> 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

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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message