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

JOC should not handle an invalid session as an error

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 1.12.4
    • None
    • None

    Description

      Current Situation

      When a user is logged in, the back-end process is stopped and then started again and then the user clicks on a button/link on the JOC, then the JOC logs following messages:

      2018-06-08T11:51:49.343+0200 xevws004 JobSchedulerGui-1_027 joc ERROR                  JOCDefaultResponse.java   291        qtp110718392-15  Authentication failure: Session doesn't exist
2018-06-08T11:51:49.344+0200 xevws004 JobSchedulerGui-1_027 joc  INFO                  JOCDefaultResponse.java   123        qtp110718392-15  SessionNotExistException: Session doesn't exist

      Both messages say at the end: Session doesn't exist
      But one has severity ERROR and the other has severity INFO.

      Desired Behavior

      When a user is logged in, the back-end process is stopped and then started again and then the user clicks on a button/link on the JOC, then JOC should not log with severity ERROR

      2018-06-08T11:51:49.343+0200 xevws004 JobSchedulerGui-1_027 joc INFO                  JOCDefaultResponse.java   291        qtp110718392-15  Authentication failure: Session doesn't exist
2018-06-08T11:51:49.344+0200 xevws004 JobSchedulerGui-1_027 joc  INFO                  JOCDefaultResponse.java   123        qtp110718392-15  SessionNotExistException: Session doesn't exist

      Attachments

        Activity

          People

            ur Uwe Risse
            ur Uwe Risse
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: