Return-Path: 
 <tomcat-user-return-127671-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 31020 invoked from network); 26 May 2005 21:06:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 26 May 2005 21:06:29 -0000
Received: (qmail 95948 invoked by uid 500); 26 May 2005 21:06:09 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 95922 invoked by uid 500); 26 May 2005 21:06:09 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 95907 invoked by uid 99); 26 May 2005 21:06:09 -0000
X-ASF-Spam-Status: No, hits=1.0 required=10.0
	tests=FORGED_RCVD_HELO,HTML_50_60,HTML_MESSAGE,PLING_QUERY,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of
 Rossen.Angelov@sourcemedia.com designates 207.241.10.34 as permitted sender)
Received: from tmgate2.thomsonmedia.com (HELO tmgate2.thomsonmedia.com)
 (207.241.10.34)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 26 May 2005 14:06:07 -0700
Received: from tmskoex01.tm.thomsonmedia.com (ip-33.bankinfo.com
 [207.241.10.33])
	by tmgate2.thomsonmedia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
 j4QL64pP017163
	for <tomcat-user@jakarta.apache.org>; Thu, 26 May 2005 16:06:04 -0500 (CDT)
Received: by tmskoex01.thomsonmedia.com with Internet Mail Service
 (5.5.2657.72)
	id <LDKFD00K>; Thu, 26 May 2005 16:06:04 -0500
Message-ID: 
 <4F8DDDFDAC9A864AAED5BB875129DF4B0690CCD6@tmskoex01.thomsonmedia.com>
From: "Angelov, Rossen" <Rossen.Angelov@SourceMedia.com>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Subject: RE: servlet request time out ?!
Date: Thu, 26 May 2005 16:06:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C56236.BA60223A"
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C56236.BA60223A
Content-Type: text/plain;
	charset="iso-8859-1"

Well, I know only two attributes in Tomcat that configure connection related
timeouts: connectionTimeout and disableUploadTimeout.

I already tried setting connectionTimeout=0 but it didn't work. Now I'll try
setting disableUploadTimeout=true. I didn't have it before in my server.xml
and by default it's set to "false", so hopefully this works.

Any suggestions are welcome if anybody else knows other timeouts for the
request.

Thanks,
Ross

-----Original Message-----
From: Mike Baliel [mailto:mbaliel@atomogy.com]
Sent: Thursday, May 26, 2005 3:37 PM
To: Tomcat Users List
Subject: Re: servlet request time out ?!


Hi Angelov,

	I had a similar problem a few years back using websphere 4.0 and
IBM's 
HTTP server.  The HTTP server was dropping the connection with the 
servlet container before the unit of work had finished.  Setting the 
HTTP server's connection timeout to "infinite" resolved the issue.

Not sure if it will work here... but it is worth a try..



Angelov, Rossen wrote:
> That's exactly how I understood it too. The request will be dropped if
after
> certain number of milliseconds the request's URI hasn't been received.
> 
> In my case the URI comes directly with the request and based on my log I
can
> see the request is being processed but there is no response after the
doPost
> method is finished.
> 
> I can still give it try with connectionTimeout="0", but don't expect it to
> help.
> 
> Ross
> 
> -----Original Message-----
> From: Steve Kirk [mailto:tomcat-user@web-startup.co.uk]
> Sent: Thursday, May 26, 2005 3:09 PM
> To: 'Tomcat Users List'; mbaliel@atomogy.com
> Subject: RE: servlet request time out ?!
> 
> 
> 
> I haven't tested this myself, so I'm only going on what the docs say
(5.5): 
> http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html 
> 
> If I've understood correctly, this doc seems to say that the
> connectionTimeout param doesn't have the effect Angelov is looking for -
it
> sets the max time between a connection (socket) being opened by the
client,
> and the client sending a request url to TC.
> 
> 
>>-----Original Message-----
>>From: Mike Baliel [mailto:mbaliel@atomogy.com] 
>>Sent: Thursday 26 May 2005 19:49
>>To: Tomcat Users List
>>Subject: Re: servlet request time out ?!
>>
>>
>>Hi Angelov,
>>
>>	I am new to Tomcat (Just started using Tomcat5.0 
>>yesterday), but the 
>>problem you mentioned sounds like a typical connnection timout.
>>
>>Have you tried to setting the connectionTimeout value to 0 in the 
>>server.xml?
>>
>>Here is to location in server.xml.  Where there is currently 
>>a value of 
>>[connectionTimeout="20000"] change to [connectionTimeout="0"].
>>
>>
>>
>>  <Service name="Catalina">
>>
>>     <!-- A "Connector" represents an endpoint by which requests are 
>>received
>>          and responses are returned.  Each Connector passes 
>>requests on 
>>to the
>>          associated "Container" (normally an Engine) for processing.
>>
>>          By default, a non-SSL HTTP/1.1 Connector is established on 
>>port 8080.
>>          You can also enable an SSL HTTP/1.1 Connector on 
>>port 8443 by
>>          following the instructions below and uncommenting 
>>the second 
>>Connector
>>          entry.  SSL support requires the following steps 
>>(see the SSL 
>>Config
>>          HOWTO in the Tomcat 5 documentation bundle for more detailed
>>          instructions):
>>          * If your JDK version 1.3 or prior, download and 
>>install JSSE 
>>1.0.2 or
>>            later, and put the JAR files into 
>>"$JAVA_HOME/jre/lib/ext".
>>          * Execute:
>>              %JAVA_HOME%\bin\keytool -genkey -alias tomcat 
>>-keyalg RSA 
>>(Windows)
>>              $JAVA_HOME/bin/keytool -genkey -alias tomcat 
>>-keyalg RSA 
>>(Unix)
>>            with a password value of "changeit" for both the 
>>certificate and
>>            the keystore itself.
>>
>>          By default, DNS lookups are enabled when a web 
>>application calls
>>          request.getRemoteHost().  This can have an adverse impact on
>>          performance, so you can disable it by setting the
>>          "enableLookups" attribute to "false".  When DNS lookups are 
>>disabled,
>>          request.getRemoteHost() will return the String 
>>version of the
>>          IP address of the remote client.
>>     -->
>>
>>     <!-- Define a non-SSL Coyote HTTP/1.1 Connector on the 
>>port specified
>>          during installation  -->
>>     <Connector
>>port="8080"               maxThreads="150" minSpareThreads="25" 
>>maxSpareThreads="75"
>>                enableLookups="false" redirectPort="8443" 
>>acceptCount="100"
>>                debug="0" connectionTimeout="20000"
>>                disableUploadTimeout="true" />
>>     <!-- Note : To disable connection timeouts, set 
>>connectionTimeout value
>>      to 0 -->
>>
>>
>>Mike
>>
>>Angelov, Rossen wrote:
>>
>>>Hi,
>>>Does anybody know about a time out on a servlet request 
>>
>>with Tomcat 5?
>>
>>>The problem is that I have a request that takes about 30 
>>
>>minutes but the
>>
>>>browser keeps waiting for the response forever. I tried 
>>
>>different browsers
>>
>>>but it's the same behavior.
>>>
>>>I put debug statements in the doPost method and it's 
>>
>>finishing correctly.
>>
>>>The last debug statement is printed out but the browser is 
>>
>>still waiting for
>>
>>>the response.
>>>
>>>Ross
>>>
>>>"This communication is intended solely for the addressee and is
>>>confidential and not for third party unauthorized distribution."
>>>
>>>
>>>
>>>
>>>
>>
>>--------------------------------------------------------------
>>----------
>>
>>>No virus found in this incoming message.
>>>Checked by AVG Anti-Virus.
>>>Version: 7.0.322 / Virus Database: 266.11.17 - Release 
>>
>>Date: 5/25/2005
>>
>>
>>-- 
>>No virus found in this outgoing message.
>>Checked by AVG Anti-Virus.
>>Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005
>>
>>
>>---------------------------------------------------------------------
>>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
> 
> "This communication is intended solely for the addressee and is
> confidential and not for third party unauthorized distribution."
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.17 - Release Date: 5/25/2005


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

"This communication is intended solely for the addressee and is
confidential and not for third party unauthorized distribution."


------_=_NextPart_001_01C56236.BA60223A--