Uploaded image for project: 'JOC - JobScheduler Operations Center'
  1. JOC - JobScheduler Operations Center
  2. JOC-1033

JOC Cockpit should not throw an exception on using äöüÄÖÜ in job parameter value

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.12, 1.13
    • 1.12.15, 1.13.7
    • None
    • None

    Description

      Current Situation

      When using the äöüÄÖÜ character in the job parameter from the JOC-Cockpit. The error message occurred:

      JOC-400
      JobSchedulerBadRequestException: XmlException: com.fasterxml.aalto.WFCException: Unexpected end-of-input when trying to parse START_ELEMENT at [row,col {unknown-source}]: [1,65] - In <sos.spooler.variable_set> (:1:1)
      

      How to Reproduce

      • Login to the JOC-Cockpit.
      • Click on Jobs tabs view.
      • Start any standalone job using the option "Start Task Parameterized" from the action menu of the job.
      • Add a new parameter with the name "A" and value "äöü".
      • Submit the task.
      • The JOC-Cockpit throws the above mention exception.

      Desired Behavior

      It should be possible to handle the job parameter with äöüÄÖÜ as a value from the JOC Cockpit.

      Workaround

      This issue depends on the used characterset in the database table field SCHEDULER_HISTORY.PARAMETERS.
      An "ALTER TABLE" statement solves this issue. The characterset 'Latin1' is necessary.
      Here the MySQL statements:

      to remove already existing corrupted parameters
      update SCHEDULER_HISTORY set "PARAMETERS" = null where "PARAMETERS" is not null and "PARAMETERS" not like '%</sos.spooler.variable_set>%';
      
      to change the charset
      ALTER TABLE SCHEDULER_HISTORY MODIFY "PARAMETERS" LONGTEXT CHARACTER SET latin1;
      

      Attachments

        Activity

          People

            oh Oliver Haufe
            Aditi-Dubey Aditi Dubey (Inactive)
            Aditi Dubey Aditi Dubey (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: