Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: "Antony Paul" <antonypaul24@hotmail.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
References: <LAW12-OE68ccYTjr8cU00000468@hotmail.com>
 <3FBE1656.9060408@comcast.net>
Subject: Re: Severity less - DBCP not closing connection.
Date: Mon, 24 Nov 2003 10:41:53 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <LAW12-OE71eV9fzG8j900002067@hotmail.com>

    Thanks a lot for the info.
    I need more explanation. I thought that Tomcat creates a new thread to
serve the new request and continues execution of the current servlet thread
after a forward() or redirect(). Now you mean that only after the forward()
method is completed the control returns to the calling servlet.. If the
servlet to which it is forwareded takes lot of time to complete then what
will happen ?. This is not mentioned in any articles or books that I have
read.

Antony Paul.

----- Original Message -----
From: "Christopher Schultz" <christopher.d.schultz@comcast.net>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Friday, November 21, 2003 7:12 PM
Subject: Re: Severity less - DBCP not closing connection.


> Antony,
> >     I have seen DBCP not closing a connection if the request is
forwarded to
> > same page in the try block before the request is forwarded. With
> > sendRedirect no problem.
>
> If you execute a "forward", then it acts just like a method call -- your
> connection will still be absent from the pool. When you forward, you
> exit your try/catch block before the browser makes the next request.
>
> You have to do your code like this:
>
> try
> {
> conn = ...;
> }
> catch (...)
> {
> }
> finally
> {
> conn.close();
> }
>
> requestDispatcher.forward(...);
> ========================================
>
> Otherwise you might deadlock your application.
>
> > I work with one connection to test for connection leak and any
bottlenecks
> > in code.
>
> This is a very good idea.
>
>  > It works fine if I put the forward() after the end of finally
> > block. I want to know whether it is bug or config error or Tomcat
behaves
> > so.
>
> This is a logic error - not a Tomcat bug or config error. You just have
> to write more careful code.
>
> -chris
>
>
> ---------------------------------------------------------------------
> 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