Thanks for the response.

I am using the "getConnection(request)" method to get the connection
and then "connection.close()" to close the connection.

"getConnection()" and "close()" both are in library files provided by struts
(DBCP).
Therefore it is difficult to put the counter in these methods.
Any idea how can we put the counters in these methods?
Or there is any way in which if i increase the DEBUG level and investigate the
log file generated by Tomcat (catalina.out)

Riyad Kalla wrote:

> This may seem to simplistic, but you could do a search for whichever
> method you call to open a connection and then do a search for
> connection.close() (or whatever you named the variable) and see if the
> numbers add up... if they don't, this might help you narrow down which
> file the two aren't syncronous with eachother.
>
> Like I said though, this is the brute-force approach, I don't know a
> 'good' way to do this off hand.
>
> On Wed, 09 Jun 2004 11:14:40 +0530, Shailender Jain
> <[EMAIL PROTECTED]> wrote:
> >
> > I have fished developing the application using Struts and Tomcat 5.0.16
> > as server.
> >
> > We used the Connection Pooling provided by Struts (DBCP)
> >
> > After the development we have realized that somewhere in the application
> > the connection is not
> > getting closed. Due to this the application is getting hang very
> > frequently. We have actually assumed that the application gets hang due
> > to
> > this reason only.
> >
> > Is there any way to DEBUG where in the application where the connection
> > is not getting closed.
> >
> > Regards
> > Shailender Jain
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to