Thanks guys!
I went through the code last night, after sending the e-mail. I think I found
the problem. Our developer uses dynamically included JSP declaring
session=true (by not declaring anything) while the parent declares
session=false.
We'll go through a set of tests anyway. I'm ashamed
Hi all,
We're running Tomcat 4.1.24 on Win2K sp4. After a few days of use (usually 4-5
days), Tomcat comes to a semi-halt mode and it refuses to process some of the
pages. Even the thrown exceptions are not logged. It looks like it's a thread
pool related problem because, apparently, the
[EMAIL PROTECTED] wrote:
Hi all,
We're running Tomcat 4.1.24 on Win2K sp4. After a few days of use (usually 4-5
days), Tomcat comes to a semi-halt mode and it refuses to process some of the
pages. Even the thrown exceptions are not logged. It looks like it's a thread
pool related problem because,
Well, this is a valid error, and doesn't indicate a problem.
Remy,
Thanks for your prompt answer. Please don't get me wrong, I don't want to sound
arrogant or something, but how come an error may not indicate a problem. ;-)
We've already gotten the thread dump. I'll have a look into that
The stack trace you posted has to do with committing the reponse (which
actually means sending data back to the client instead of sitting in a
buffer), then trying to allocate a session. Allocating a NEW session involves
sending a cookie back to the client to let the client be aware of the new
[EMAIL PROTECTED] wrote:
Thanks for your prompt answer. Please don't get me wrong, I don't want to sound
arrogant or something, but how come an error may not indicate a problem. ;-)
It indicates there's likely a bug in the app, not in TC (that's what I
meant). You can't create a session if the
