Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-14887

TimerPool logs error during AM graceful shutdown

    Details

    • Sprint:
      FRaaS 2019.7, AM 2020.11 - Trip Hammer, AM 2020.13 - Aeolipile

      Description

      Bug description

      During graceful shutdown, AM's TimerPool logs an error for each thread which it needs to interrupt to prompt its shutdown. Unfortunately, the error message doesn't log the threads name (only its thread ID) so it's difficult to establish whether or not this truly is a problem.

      This issue is seen when running AM in Kubernetes on GCP as part of the saas.

      How to reproduce the issue

      1. Start one or more AM pods in Kubernetes.
      2. Tail the logs from an AM pod using kubectl logs -f <am pod name> -c openam
      3. Delete AM pod using GCP console
      Expected behaviour
      No errors seen in AM logs during graceful shutdown.
      
      Current behaviour
      SystemTimer:05/01/2019 10:20:06:012 AM GMT: Thread[localhost-startStop-2,5,main]: TransactionId[d6f57a65-1a76-4ec6-80bc-1d6972014998-12401] ERROR: TimerPool:shutdown() terminating remaining worker thread[29]
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ken.stubbings Ken Stubbings
                Reporter:
                craig.mcdonnell Craig McDonnell
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: