If you get an OOM error - typically - all bets are off. Pack up the JVM
- restart it and try again.
Tomcat should the log the OOM error if it catches it. If something else
if first catching and swallowing it - then tomcat doesn't have a chance
to log it.
-Tim
Ingo Siebert wrote:
Hi, thank
Hi, thank you for your answer.
Sorry, it's quite possible that the 404 code was wrong, i think it was
the 500 code.
But I'm still wondering why Tomcat (5.5) doesn't log the error
message(i.e. out of heap space) into a log file.
My logging.properties file of Tomcat isn't modified.
Ingo
Tim
Its odd that you would get a 404 for such an error but in any case:
http://tomcat.apache.org/faq/misc.html#error
-Tim
Ingo Siebert wrote:
Hi,
i'm using Tomcat 5.5 and run a JAX-WebService application.
In general, if an error occurs at my application i will send back an
SOAP-fault. So far so
Hi,
i'm using Tomcat 5.5 and run a JAX-WebService application.
In general, if an error occurs at my application i will send back an
SOAP-fault. So far so fine.
But my problem is now, that sometimes occurs an JVM/Tomcat exception
(i.e. out of heap-space) and in this case, Tomcat sends back a
