commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheng Huang <SHu...@tlg.ca>
Subject RE: [dbcp] How could I find out the application methods that hold the active connections?
Date Thu, 15 Apr 2004 14:13:47 GMT
Hi Dirk,

Thank you very much for your reply. However, I am running my application on
a Linux box. I always use ./catalina.sh start because the Tomcat process
started with "./catalina.sh run" or "./catalina.sh run &" will get
terminated when the shell window timeouts or gets closed. 

Is there a workaround with "./catalina.sh run" so that I can redirect the
stderr log? Thank you very much.

Best regards,
Sheng

-----Original Message-----
From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
Sent: April 14, 2004 2:13 PM
To: Jakarta Commons Users List
Subject: Re: [dbcp] How could I find out the application methods that
hold the active connections?


Try:
    catalina run >stdout.log 2>stderr.log

Cheers
Dirk


Sheng Huang wrote:

> Hi Dirk,
> 
> Thank you very much for your reply. Now I understand the connections
closed
> in my configuration are active connections instead of inactive
connections.
> Although I see a lot of "DBCP object created was never
> closed" followed by "Already closed" as I said in my first email, all
> connections will become active after the application is used for some time
> and then the application stalls (wait unlimited for available
connections).
> 
> There may be some defects in my code, thus the stacktrace for DBCP object
> creation will be very helpful to me. Since I just installed Tomcat 4.1.18
> with the default configuration (standalone Tomcat instead of Tomcat and
> Apache), I can't see the stderr messages logged somewhere and don't know
how
> to set it up. Could you give me some information on how to setup stderr
> logging or redirect them to the standard catalina.out? Thank you very
much.
> 
> Best regards,
> Sheng
>   
> 
> 
> When you get a "DBCP object created..." message then there should also be
a
> stacktrace be written. With version 1.1 the message goes to stdout and the
> stacktrace to stderr. In the nightly builds they go both go to stderr.
> 
> The stacktrace displays the location where is abandoned connection was
> borrowed.
> 
> 
> The removeAbandoned parameter is for removing the active connections.
> Idle connections are removed with "minEvictableIdleTimeMillis".
> 
> -- Dirk
> 
> ---------------------------------------------------------------------
> 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