Hi, It's a dev server, but not running out of memory. (384 MB). And yes, Tomcat definitely does do weird stuff with Turbine when the web app is reloaded. (That'll be the subject of another email, once I have time to investigate).
The error is generated by the ORO library when confronted by a difficult match. I've encountered it before, and can usually work around it. Again, IMHO, In the (unexpected case) that a app (even in production) gives an error, I think it would be 100x better for a nice web designed page to come up saying "sorry-- internal error-- come back later" than for the app to just crash. (or display a "Horrible exception" page). Just a thought-- maybe the Turbine servlet should catch "Throwable" not just "Exception". Thanks again, WILL -----Original Message----- From: Phee, Martin J (Jump Tech) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 11:46 AM To: 'Turbine Users List' Subject: RE: Turbine.handleException: null Is it possible your vm is running out of memory. Try bumping up the maximum memory when you start up tomcat. I have mine at around 256MB running on w2k. I have never had tomcat crash because of a normal error, but I did have it crash because it was out of memory. Is this a development server or production? I have had tomcat do weird things on a development instance after it has restarted the web app a few times. -----Original Message----- From: Will Glass-Husain [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 1:41 PM To: Turbine Users List Subject: RE: Turbine.handleException: null sorry, meant an "error in one page to bring down my entire webapp". I vote-- not. What's the take of others? The original question is relevant too, but outside of the scope of this list. Thanks, WILL -----Original Message----- From: Will Glass-Husain [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 11:28 AM To: Turbine Users List Subject: RE: Turbine.handleException: null Okay, that's helpful info. Opinion question then-- is this reasonable for an error in one webapp to bring down my entire app server? WILL -----Original Message----- From: Scott Brickner [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 11:22 AM To: 'Turbine Users List' Subject: RE: Turbine.handleException: null Remember there are three major subclasses of Throwable: Error, Exception, and RuntimeException. The Error subclass is unchecked (like RuntimeException), but it's *not* a subclass of Exception. StackOverflowError is an Error. Nothing is catching it, even in the Tomcat code. This is usuall reasonable, as Errors are supposed to indicate something "really" wrong with the JVM. Out of memory, invoking an abstract method, referencing fields or methods that don't exist, class files not verifying, that kind of stuff. -----Original Message----- From: Will Glass-Husain [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 12:14 PM To: [EMAIL PROTECTED] Subject: Turbine.handleException: null 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
