>
> If this measurement is made from the point of view of the DB server (I don't 
> think the OP ever said), the number if fine.
Actually if you look at the code in the OPs original post, you'll see
how the measurement is being made.  It's essentially:


>     public static DataSource getDataSource() throws SQLException {
>         (snip ...)
>                 ds = 
> (BasicDataSource)initContext.lookup("java:/comp/env/jdbc/myDB");
>         (snip ....)
>         }
>     
>     private static void logDataSource(final BasicDataSource ds) {
>         (snip ...)
>         DATASOURCE.info("The number of active connections are : " + 
> ds.getNumActive());
>         DATASOURCE.info("The number of idle connections are : " + 
> ds.getNumIdle());
>         (snip ...)        
>     }

The numbers appear to be coming from the DBCP BasicDataSource itself.

--David

Caldarale, Charles R wrote:
>> From: Johnny Kewl [mailto:[EMAIL PROTECTED]
>> Subject: Re: Tomcat 5.5, JNDI Connection Pooling, Active
>> connections keep increasing....
>>
>> sinoea, of course you can... that looks thread safe... but
>> what I'm trying to do, is just make it bullet proof...
>>     
>
> Your suggestion does nothing to improve reliability, it just slows things 
> down by creating completely unnecessary do-nothing objects.
>
>   
>> You leaking connections, we dont know why...
>>     
>
> Actually we don't know it's leaking connections.  All we know is that 
> somewhere in the overall system the number of connections is seen to be 37.  
> If this measurement is made from the point of view of the DB server (I don't 
> think the OP ever said), the number if fine.  DBCP keeps the real connections 
> open for as long as the DB server permits; it's only if requests stall 
> because all the connections are busy (in use by other requests), then there's 
> a leak.  I haven't read anything yet that indicates that's the case here.
>
>  - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
> MATERIAL and is thus for use only by the intended recipient. If you received 
> this in error, please contact the sender and delete the e-mail and its 
> attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to