And... as most are coming around to... we think you need to examine the
900lb gorilla in the room: the code.
>> I've seen a certain web browser get hold of some badly-written script
or something,
>> spend *minutes* blowing up to a huge size while running 100% of CPU
the whole time
>> with the UI completely unresponsive
There are many bad results that can produce this, such as entity
recursion, XML x-Ref, XSS, etc., so depending upon how the code produces
the actual result, you cannot know.
I still think that, since it runs the first time, then fails on the next
or next subsequent hit, that something is 1) Caching and 2) Ignoring
exceptions (as was previously suggested).
To ignore an OutOfMemory error, the code needs to be written something
like this:
try { ... }
catch (Throwable t) {}
However, Throwable can be replaced with any of "Error" or
"VirtualMachineError" or "OutOfMemoryError".
try { ... }
catch (Exception e) {}
won't work to catch an OutOfMemory error, because they are not in the
same class hierarchy. Since you are getting nothing in the logs, I
suspect there is a
try { ... }
catch (Throwable t) {}
somewhere effectively "hiding" the error. That is, the code block
following the catch may not be empty, but contains nothing that signals
that something bad has happened, such as writing to the logs.
-----Original Message-----
From: Mark H. Wood [mailto:mw...@iupui.edu]
Sent: Thursday, February 11, 2010 9:30 AM
To: users@tomcat.apache.org
Subject: Re: JSP Page "hangs"... clues?
On Wed, Feb 10, 2010 at 12:26:42PM -0800, Jordan Michaels wrote:
> Yeah, it's hanging permanently. We've let it sit there for what... 15
> mins or so? Which should be plenty since no one is using it right now
> except us.
Maybe, maybe not. Did you monitor CPU and memory utilization, I/O load
and I/O wait time on the server during one of these spells? I've seen a
certain web browser get hold of some badly-written script or something,
spend *minutes* blowing up to a huge size while running 100% of CPU the
whole time with the UI completely unresponsive, then give all that
memory back and continue as if nothing had happend.
Maybe you've found a way to do something similar with Tomcat, but it
takes 16 minutes to cycle.
Just waiting until you think it's been long enough is not a very strong
test. What's it doing while you wait? is a question you need to
consider.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Friends don't let friends publish revisable-form documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
