commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <dirk.verbe...@pandora.be>
Subject Re: [DBCP] Deadlock problem?
Date Wed, 03 Dec 2003 18:00:09 GMT
8 connections is the default maxActive

You can also use the following page to get the number of active/idle 
connections from the perspective of the database pool:
http://cvs.apache.org/~dirkv/builds/showJNDI.jsp

-- Dirk

Frank Stolze wrote:
> Dirk,
> 
> Thank you for your follow-up. I did restart the server between those
> thread dumps. They represent the server being in a "hung" state, at
> different instances.
> 
> In terms of database connections, at that point in time I usually see 4
> to 6 connections, all of them in an idle state. The database server
> allows 128 connections, and DBCP was at the default setting (8 I
> believe?).
> 
> I will generate several dumps when I catch another event like this.
> 
> Regards,
> Frank
> 
> 
> On Tue, 2003-12-02 at 18:07, Dirk Verbeeck wrote:
> 
>>Actually I don't see a deadlock in the stack traces you provided.
>>I see two times 2 threads waiting for a connection
>>
>>In the first dump a getConnection from a <c:out> in your products.jsp page and

>>from CSVGenerator called in DataFileGeneratorServlet.
>>
>>The second dump again in the CSVGenerator but a different place and also the 
>>products.jsp page.
>>
>>You probably did restart the server between the two threaddumps?
>>Please make a couple of threaddumps with 30 sec inbetween without restarting.
>>
>>How did you test the number of available database connections?
>>
>>-- Dirk
>>
>>Frank Stolze wrote:
>>
>>
>>>Hi,
>>>
>>>I have been having some problems with Tomcat + DBCP for some time now. I
>>>made every effort to find the problem myself and also look through the
>>>mailing list archives, but it seems that I'm at a dead end now. Here is
>>>my problem:
>>>
>>>Tomcat 4.1.27
>>>Commons-Pool 1.1
>>>Commons-DBCP 1.1
>>>PostgreSQL 7.3.3
>>>
>>>While everything works beautifully for a while, at some (seemingly)
>>>random point in time getting a db connection from the pool fails.
>>>Database connections are available, both idle and not yet established.
>>>
>>>Configuration:
>>>
>>>          <Resource auth="Container" name="jdbc/Public"
>>>scope="Shareable" type="javax.sql.DataSource"/>
>>>          <ResourceParams name="jdbc/Public">
>>>            <parameter>
>>>              <name>password</name>
>>>              <value>xxxx</value>
>>>            </parameter>
>>>            <parameter>
>>>              <name>url</name>
>>>              <value>jdbc:postgresql://localhost:5432/bfth_db</value>
>>>            </parameter>
>>>            <parameter>
>>>              <name>driverClassName</name>
>>>              <value>org.postgresql.Driver</value>
>>>            </parameter>
>>>            <parameter>
>>>              <name>username</name>
>>>              <value>xxxx</value>
>>>            </parameter>
>>>          </ResourceParams>
>>>
>>>Here are two representative thread dumps:
>>
>>threaddumps removed
>>
>>
>>>Any advice would be appreciated!
>>>
>>>
>>>Frank
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
> 
> 
> 
> 



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


Mime
View raw message