No - its a printStackTrace() that is being used - we dont use getMessage() at that point at all - if we had it would be in the stdout log though - we only use System.out for debugging messages.
-----Original Message----- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2003 2:03 PM To: Tomcat Users List Subject: Re: Irregular error dumped to stderr without a stack trace. Are you sure this isn't being done: System.out.println(e.getMessage()); Which (I think) will print "java.lang.NullPointer" and nothing else similar to the behavior your getting. -Tim [EMAIL PROTECTED] wrote: > Yoav, > > If that were the case the report should bomb out every time it was ran on > the same set of data - which its not :( > > There is a catch in the base servlet that should throw a stack trace for ANY > error. > After some more debugging, the exception is being caught by this base > Exception catch (identified by a System.out) - but like I said, the > stacktrace is being truncated to the first line of it for some reason. > Normally this would provide a full stack trace. > > Steve > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
