Identifying and Communicating Errors

Software errors may be distinguished as follows:

• Terminal errors may be identified in software logs by searching for ERROR (no quotes, case sensitive).

• Non-Terminal errors (warnings) may be identified in software logs by searching for WARN (no quotes, case sensitive).

Additionally:

• See the steps in Accessing Software Logs for how to search software logs.

• There may be more than one log line related to a given issue (use co-located date and time to isolate).

• Lines indicating errors in software log files are commonly approximate to stack trace text. For more information, see Stack Trace. This text may be important for optimizing support interactions and issue resolution. Therefore, be sure to either include stack trace text (or) entire log files when reporting issues.

The following is an example of a terminal error with (a) two related log lines and (b) a stack trace from a log file:

2019-05-28 09:42:02,901 ERROR [JobParserWorkflowService] Unable to parse file (message: Invalid input 
line:
^B^A^A^@^@^@^@^@^@^@^@^@^C^@>^@^A^@^@^@@F^@^@^@^@^@^@@^@^@^@^@^@^@^@'! 
^B^@^@^@^@^@^@^@^@^@@^@8^@',      source: 2019-05-28T16:41:43Z-POSD0126). 
(will report to JAWS; schedulerId=(none), transactionId=(none), 
errorType=GENERAL).
2019-05-28 09:42:04,294 ERROR [FileReaderMonitorService] Can not parse file 
(stream error): ParserWorkflowException(lineCtr=1, inputText=[]) 
com.termalabs.connector.jobtrac.service.ParserWorkflowException: Invalid 
input 
line:^B^A^A^@^@^@^@^@^@^@^@^@^C^@>^@^A^@^@^@@F^@^@^@^@^@^@@^@^@^@^@^@^@^@'!
^B^@^@^@^@^@^@^@^@^@@^@8^@ '
     at
com.termalabs.connector.jobtrac.service.job.JobParserService.handleExceptio
n(JobParserService.java:411) ~[classes!/:?] 
     at
com.termalabs.connector.jobtrac.service.job.JobParserService.parseNextJob(J
obParserService.java:305) ~[classes!/:?]
     at
com.termalabs.connector.jobtrac.service.job.JobParserService.access$000(Job 
ParserService.java:74) ~[classes!/:?] 

[...]