Job Scheduler

Certain Strings in order log (or stdout) can cause the Job Scheduler to go into an infinite loop and stop processing and responding

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.3.1
  • Fix Version/s: 1.3.2
  • Component/s: Job Scheduler Binaries
  • Description:
    Hide

    The order log contains the line:
    08:42:54.376 scheduler 0 1740.6C8 206.348MB .{scheduler} [info] (Task RCH_mail_handled_orders_job:534) DEBUG | monitoring.writer.ScriptBasedWriter | Tivoli script command: D:/ws/ALMSOSScheduler/ALMSOSSchedulerConfig/dist/devel//bin\send_event_java_Test.bat HARMLESS req06915.ad.raiffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:40:53.919 SOSScheduler core Heartbeat - every 5s

    This (along with the rest of the log) is stored in ORDER_XML of SCHEDULER_ORDERS. When reading ORDER_XML, this causes an error:
    08:42:56.595 scheduler 0 1740.6C8 206.340MB ..jdbc: prepareStatement SELECT "ORDER_XML" FROM SCHEDULER_ORDERS where "ID"='35' and "JOB_CHAIN"='RCH_calculationChain_singleton' and "SPOOLER_ID"='req09615_ALMScheduler'
    08:42:56.610 scheduler 16 1740.6C8 206.340MB .[ERROR LIBXML2 [:2: validity error : Validation failed: no DTD found !
    08:42:56.610 scheduler 0 1740.6C8 206.340MB .<order touched="yes" start_time="2007-07-18 08:42:52.095"><log>2007-07-18 08:42:
    08:42:56.610 scheduler 0 1740.6C8 206.340MB . ^
    08:42:56.610 scheduler 0 1740.6C8 206.340MB .:58: parser error : internal error
    08:42:56.610 scheduler 0 1740.6C8 206.340MB .ffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:42:52.907 SOSScheduler core Heartbeat
    08:42:56.610 scheduler 0 1740.6C8 206.340MB . ^
    08:42:56.610 scheduler 0 1740.6C8 206.340MB .:58: parser error : Extra content at the end of the document
    08:42:56.610 scheduler 0 1740.6C8 206.340MB .ffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:42:52....]]

    If the line is removed from the log, everything runs fine

    Show
    The order log contains the line: 08:42:54.376 scheduler 0 1740.6C8 206.348MB .{scheduler} [info] (Task RCH_mail_handled_orders_job:534) DEBUG | monitoring.writer.ScriptBasedWriter | Tivoli script command: D:/ws/ALMSOSScheduler/ALMSOSSchedulerConfig/dist/devel//bin\send_event_java_Test.bat HARMLESS req06915.ad.raiffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:40:53.919 SOSScheduler core Heartbeat - every 5s This (along with the rest of the log) is stored in ORDER_XML of SCHEDULER_ORDERS. When reading ORDER_XML, this causes an error: 08:42:56.595 scheduler 0 1740.6C8 206.340MB ..jdbc: prepareStatement SELECT "ORDER_XML" FROM SCHEDULER_ORDERS where "ID"='35' and "JOB_CHAIN"='RCH_calculationChain_singleton' and "SPOOLER_ID"='req09615_ALMScheduler' 08:42:56.610 scheduler 16 1740.6C8 206.340MB .[ERROR LIBXML2 [:2: validity error : Validation failed: no DTD found ! 08:42:56.610 scheduler 0 1740.6C8 206.340MB .<order touched="yes" start_time="2007-07-18 08:42:52.095"><log>2007-07-18 08:42: 08:42:56.610 scheduler 0 1740.6C8 206.340MB . ^ 08:42:56.610 scheduler 0 1740.6C8 206.340MB .:58: parser error : internal error 08:42:56.610 scheduler 0 1740.6C8 206.340MB .ffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:42:52.907 SOSScheduler core Heartbeat 08:42:56.610 scheduler 0 1740.6C8 206.340MB . ^ 08:42:56.610 scheduler 0 1740.6C8 206.340MB .:58: parser error : Extra content at the end of the document 08:42:56.610 scheduler 0 1740.6C8 206.340MB .ffeisen.ch JavaAppl_HB 1.0 2007-07-18 08:42:52....]] If the line is removed from the log, everything runs fine
  1. bad_order.zip
    (47 kB)
    Andreas Liebert
    18 July 2007 12:12

Issue Links

Activity

Hide
Andreas Liebert added a comment - 18 July 2007 17:58

The String which causes the error contains ASCII character 1A

Show
Andreas Liebert added a comment - 18 July 2007 17:58 The String which causes the error contains ASCII character 1A
Hide
Andreas Liebert added a comment - 04 December 2007 10:44

libxml error occured again

Show
Andreas Liebert added a comment - 04 December 2007 10:44 libxml error occured again
Hide
Joacim Zschimmer added a comment - 11 December 2007 20:15

scheduler 2.0.192.5428 (2007-12-11): Ich konnte den zweiten Fehler nicht nachvollziehen, es hängt anscheinend auch von der Datenbank ab. Jedenfalls habe ich eine verantwortliche Stelle gesehen, die das XML-Dokument zerschneiden konnte. Der neue Scheduler tut das nicht mehr.

Show
Joacim Zschimmer added a comment - 11 December 2007 20:15 scheduler 2.0.192.5428 (2007-12-11): Ich konnte den zweiten Fehler nicht nachvollziehen, es hängt anscheinend auch von der Datenbank ab. Jedenfalls habe ich eine verantwortliche Stelle gesehen, die das XML-Dokument zerschneiden konnte. Der neue Scheduler tut das nicht mehr.

People

Dates

  • Created:
    18 July 2007 12:02
    Updated:
    11 December 2007 20:15
    Resolved:
    11 December 2007 20:15