tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: Irregular error dumped to stderr without a stack trace.
Date Fri, 26 Sep 2003 18:13:03 GMT

Howdy,

>If that were the case the report should bomb out every time it was ran
on
>the same set of data - which its not :(

The above suggests a thread contention or race condition type issue.

>There is a catch in the base servlet that should throw a stack trace
for
>ANY
>error.

So it does
try {
 ...
} catch (Throwable t) {
  System.out.println(t);
  t.printStackTrace();
}

Or something similar?

Yoav Shapira

>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
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>Sent: Friday, September 26, 2003 1:47 PM
>To: Tomcat Users List
>Subject: RE: Irregular error dumped to stderr without a stack trace.
>
>
>
>Howdy,
>Do you use System.out/System.err to log in your app?
>
>Could it simply be an uncaught null pointer exception in your report
>generation code due to some bad data contents in the report?
>
>Yoav Shapira
>Millennium ChemInformatics
>
>
>>-----Original Message-----
>>From: SMcGarrity@eschoolsolutions.com
>>[mailto:SMcGarrity@eschoolsolutions.com]
>>Sent: Friday, September 26, 2003 1:37 PM
>>To: tomcat-user@jakarta.apache.org
>>Subject: Irregular error dumped to stderr without a stack trace.
>>
>>Hi there,
>>
>>I have spent a bit of time trying to figure out why this problem is
>>happening with no luck - so I decided to email the mailing list.
>>
>>The issue is this:
>>
>>We have a PDF reporting engine running from Tomcat 4.1.24 - in a
>Production
>>environment.
>>I have a particular report that is erroring out irregularly -
sometimes
>it
>>will run 3-4 times in a row and
>>then it will bomb out (this is after re-starting the tomcat service),
>other
>>times it will bomb out after restart
>>immediately.  The weird thing is is the error that is being dumped to
>the
>>stderr log does NOT have a stack
>>trace - it is dumping with:
>>
>>java.lang.NullPointerException
>>
>>on stderr.  This reminds me of the OutOfMemoryError which dumps
without
>a
>>stack trace, but slightly
>>less descriptive.  Is there any way to get more description on this
>>problem?
>>I have tried to up
>>the debug levels in the server.xml without any success.
>>
>>NOTE Other reports that are larger and more resource intensive are
>running
>>consistently without a hitch.
>>
>>Thanks in advance,
>>Steve
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary
>and/or privileged.  This e-mail is intended only for the individual(s)
to
>whom it is addressed, and may not be saved, copied, printed, disclosed
or
>used by anyone else.  If you are not the(an) intended recipient, please
>immediately delete this e-mail from your computer system and notify the
>sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org



This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


Mime
View raw message