Just FYI to those that were following this thread, this was a Cocoon (2.1.5)
issue that caused this, not Tomcat.
Turns out that the Cocoon 2.1.5 ResourceReader sets some response headers
willy nilly.
If you have another component that uses a resolver to access a pipeline that
uses the reader
I have a situation where some requests that get sent to Tomcat are very long
running (basically batch operations). I've been testing with a request that
takes just over 7 minutes to process and returns and XML document as a
response.
The problem I'm having is that the response gets truncated.
Jan Taramina [EMAIL PROTECTED]
To: tomcat-user@jakarta.apache.org
Sent: Tuesday, January 25, 2005 2:37 PM
Subject: Long running requests and timeouts?
I have a situation where some requests that get sent to Tomcat are very
long
running (basically batch operations). I've been testing with a request
Geachte relatie,
Het door u gebruikte e-mailadres is niet meer actief. U kunt uw e-mailbericht
sturen naar [EMAIL PROTECTED] of dit bericht beantwoorden.
Bedankt voor uw medewerking,
Met vriendelijke groet,
ATP Hypotheken
Het Spoor 40
3994 AK Houten
Tel. 030 750 25 33
Fax. 030 750 25 88
I have a situation where some requests that get sent to Tomcat are very long
running (basically batch operations). I've been testing with a request that
takes just over 7 minutes to process and returns and XML document as a
response.
The problem I'm having is that the response gets truncated.
I can't answer your specific question, but the scenario you describe
raises a red flag with me in general...
When you potentially have such long-running requests, it's usual a Bad
Idea(tm) to just allow them to run like this as part of a request. I
think it's fair to say that most people
: Andrzej Jan Taramina [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 17. Januar 2005 16:25
An: tomcat-user@jakarta.apache.org
Betreff: Long running requests and timeouts?
I have a situation where some requests that get sent to Tomcat are very long
running (basically batch operations). I've been
Frank:
I don't know your usage pattern, but especially if there could be a
number of such requests coming in at once, you are tieing up server
resources this way. You also start running into situations like you
mention with timeouts (I'm actually surprised the browser itself didn't
time
what's
happening, but enough memory usually keeps these problems away...
Peiyun
-Original Message-
From: Andrzej Jan Taramina [mailto:[EMAIL PROTECTED]
Sent: January 17, 2005 1:22 PM
To: Tomcat Users List
Cc: [EMAIL PROTECTED]
Subject: Re: Long running requests and timeouts?
Frank:
I
, but enough memory usually keeps these problems away...
Peiyun
-Original Message-
From: Andrzej Jan Taramina [mailto:[EMAIL PROTECTED]
Sent: January 17, 2005 1:22 PM
To: Tomcat Users List
Cc: [EMAIL PROTECTED]
Subject: Re: Long running requests and timeouts?
Frank:
I
Ok Andrzej, sorry I couldn't be of any real help. I see what I
suggested wouldn't apply in your situation, I was just taking a guess
anyway. And certainly I understand the pressure of deadlines :)
Perhaps my approach might help someone else that's just lurking, but
good luck in solving your
I have a situation where some requests that get sent to Tomcat are very long
running (basically batch operations). I've been testing with a request that
takes just over 7 minutes to process and returns and XML document as a
response.
The problem I'm having is that the response gets truncated.
12 matches
Mail list logo
