Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of shakahshakah@gmail.com
 designates 64.233.166.183 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=pFtHKTBvdxifpzcSPt1aVRyVrjdxwI+HXMhybHfJbx6g6TbEv8A3RWodRCmqYBJ1uG+rKOaeLwGb+g520oRW0qrCDqDt3akHO/+fk2aGliNq4Eol9G0vo1gX9BlPOxzmICNvHQ4SBZHwfgqgT5DFYIViUP4lxbdQydwMjla2Iwc=
Message-ID: <c2ee6dbd0711281103x15b39a59pd53e43b157f2d62a@mail.gmail.com>
Date: Wed, 28 Nov 2007 14:03:11 -0500
From: "Jim Cox" <shakahshakah@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Tomcat hangs on writing JSP page to socket
In-Reply-To: <3c512fce0711281050k5cf8971bo1c903aeeee1a83c3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3c512fce0711281046i2b3b0193l437eb0c9873e760b@mail.gmail.com>
	 <3c512fce0711281050k5cf8971bo1c903aeeee1a83c3@mail.gmail.com>

On Nov 28, 2007 1:50 PM, Adam Feuer <adamfeuer1@gmail.com> wrote:
> Folks,
>
> We're getting intermittent problems where one tomcat thread hangs for up to
> 10 minutes writing JSP pages to a socket. We think the socket is an HTTP TCP
> socket. The stack trace from a thread dump for the hung thread is below.
>
> This happens multiple times per day at seemingly random intervals. We have
> not been able to reproduce this reliably and has been happening for as long
> as we have data (6+ months), so doesn't seem to be tied to a specific recent
> change.
>
> We run Struts 1.35, Tomcat 5.5.9, Linux 2.4.21 (Redhat) on four boxes behind
> a Netscaler load balancer. All boxes exhibit the same problem at different
> random intervals.
>
> Has anyone seen this problem? If so, do you know of a fix?
>
> -adam

FWIW, I've noticed similar behavior, but in my case it is easy to reproduce:
  1. use a browser to request a long-running and/or
large-page-producing web page ;
  2. abort the page load before it is done.

At that point I see the HTTP response thread blocked writing to the
(now closed) socket, with it timing out TCP-wise in about 8 min
(Solaris box, Tomcat 5.0.19, JDK 1.4.2_13).

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