today"
> -Original Message-
> From: Antonio Fiol Bonnin [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 21, 2004 3:42 AM
> To: Tomcat Users List
> Subject: Re: thread deadlock problem
>
>
> Christian Cryder wrote:
>
> >This works perfectly about 99% of
Christian Cryder wrote:
This works perfectly about 99% of the time. What we are observing is that
there are certain situations where we encounter a deadlock scenario (and
that's what prompted my original question). Basically, req2a writes the
redirect back to the client, the client receives the re
--
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
--
"Coffee? I could quit anytime, just not today"
> -Original Message-----
> From: Hans [mail
---
"Coffee? I could quit anytime, just not today"
> -Original Message-
> From: Hans [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 9:33 AM
> To: Tomcat Users List
> Subject: RE: thread deadlock problem
>
>
> ok,
> and can you give some more deta
-
"Coffee? I could quit anytime, just not today"
> -Original Message-
> From: Hans [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 8:21 AM
> To: Tomcat Users List
> Subject: Re: thread deadlock problem
>
>
> hi,
> is the thread mentio
t;Coffee? I could quit anytime, just not today"
> -Original Message-
> From: Hans [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 8:21 AM
> To: Tomcat Users List
> Subject: Re: thread deadlock problem
>
>
> hi,
> is the thread mentioned in 2b the sa
Hanks much,
CHristian
--
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
--
"Coffee? I could quit anytime, just not today"
> -Original Me
hi,
is the thread mentioned in 2b the same as the one that handled 2a ?
grtz
Hans
At 07:55 19/03/2004 -0500, you wrote:
Hi folks,
I need to know if someone can explain the following behavior:
1. client browser issues a request
2. tomcat servlet code starts handling the request...
a. writes an
Why are you trying to do this kind of control?
> --
> De: Christian Cryder[SMTP:[EMAIL PROTECTED]
> Responder:Tomcat Users List
> Enviada: sexta-feira, 19 de março de 2004 9:55
> Para: Tomcat-User
> Assunto: thread deadlock problem
>
Hi folks,
I need to know if someone can explain the following behavior:
1. client browser issues a request
2. tomcat servlet code starts handling the request...
a. writes an html redirect to the resp, flushes the buffer, etc
b. thread continues processing (writing to a data structure)
3.
Check out bug# 4293268 on Sun's Java bug parade. It described a 1.3
threading bug that involves lost locks. I've had similar deadlock
problem on a different app (not Tomcat) that went away when I downgraded
to Java 1.2.2.5. It is an rare problem that most occurs when a system is
"EXT-Mezey, Peter" wrote:
[Memory gobbled up fast by a search engine walking over JSP pages]
Well, if it's the same problem we had here, I'd say it's the spider
creating a new session with every request as it doesn't send back the
session-id cookie; and since it does this much faster than the ses
s and -Xmx flags to 1GB. I know it's not
running out of memory because I don't see that error message. I've tried tinkering
with the PoolTcpConnector settings in server.xml to increase the number of threads to
200. That seemed to make it run faster, but still the deadlock
13 matches
Mail list logo
