Menu

#10 Spurrious exceptions

open
Collector (2)
2
2008-06-30
2008-06-30
No

So, by far the bulk of the exceptions in the ITB log are IllegalArgumentExceptions caused by records from dCache and Brian's probe that in certain incarnations did not send the date correctly. The code handles them properly and the offending XML ends up in the ExtraXml field. One can argue over whether we need to see the exception, but everything else seems fine.

For the rest:

--------------------------------------------------------------------------------

[root@gratia09 logs]# grep ception * | grep -v IllegalArgument
(1) catalina.2008-06-24.log:INFO: Expected exception: Database '/data/tomcat-itb/temp/BIRTSampleDB_1213909036013_ac3ab/BirtSample' not found.
(2) catalina.out:java.sql.SQLException: Cannot convert value '2008-05-20 21:12:14' from column 2 to TIMESTAMP.
(3) catalina.out:org.eclipse.birt.report.exception.ViewerException: The report file : /data/tomcat-itb/webapps/gratia-reporting/test.rptdesign does not exist or contains errors.
(4) catalina.out:org.eclipse.birt.report.exception.ViewerException: The report file : /data/tomcat-itb/webapps/gratia-reporting/test.rptdesign does not exist or contains errors.
(5) catalina.out:INFO: Expected exception: Database '/data/tomcat-itb/temp/BIRTSampleDB_1213909036013_ac3ab/BirtSample' not found.

--------------------------------------------------------------------------------
(1) and (5) seem entirely benign. I'm not sure about (3) and (4) but I'm sure either Jeff or Penelope would recognize them. I don't think they're even remotely urgent. (2) is a little worrying, but not overly. It's generated by NGapStatus (presumably GOC monitoring) and it appears to be associated with a prematurely closed connection since it certainly *seems* like it should parse to a TIMESTAMP properly.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB