Hi, I have some odd behavior happen occasionally when certain errors are generated in my action code. Turbine reports the error (calling my custom Error.vm page and my ErrorScreen). Then Tomcat inexplicably shuts down, forcing me to restart the Tomcat process on my server. This is only true with some errors. With most exceptions (e.g. an index out of bound), after I get the error screen I can continue to use my app. My question is -- why do some errors crash Tomcat?
In my Turbine.log file, I see the exception and a stack trace (as listed below for a stack overflow error). My Tomcat logs contain nothing useful. I'm running on a Win XP machine with the Tomcat.exe NT service, and using Turbine 2.2b1. (Although I'll migrate the app later to a LINUX box). Tomcat version 4.0.2. Any ideas? Best, WILL [Thu Jun 13 08:59:17 PDT 2002] -- ERROR -- Turbine.handleException: null [Thu Jun 13 08:59:17 PDT 2002] -- ERROR -- Exception: java.lang.StackOverflowError Stack Trace follows: java.lang.StackOverflowError at org.apache.oro.text.regex.Perl5Matcher.__match(Perl5Matcher.java:1043) at org.apache.oro.text.regex.Perl5Matcher.__match(Perl5Matcher.java:1154) at org.apache.oro.text.regex.Perl5Matcher.__match(Perl5Matcher.java:1131) etc for about 1000 lines. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
