Confluence service from Windows services does not shut down properly

XMLWordPrintable

    • Type: Bug
    • Resolution: Tracked Elsewhere
    • Priority: Low
    • None
    • Affects Version/s: 8.7.2, 8.5.7, 8.9.1
    • None
    • 4
    • Severity 3 - Minor
    • 10

      Issue Summary

      Confluence service from Windows services does not shut down properly in Confluence v8.7.2

      Steps to Reproduce

      1. Install Confluence in Windows OS 
      2. Make sure to have Confluence run as a Windows service.
      3. Go to services.msc and stop the Confluence service.

      Expected Results

      Confluence should shutdown successfully 

      Actual Results

      Confluence does not shutdown properly and the below error is received: 

      In the application logs, we see the following lines:

      2024-02-19 15:02:47,636 INFO [Catalina-utility-2] [com.atlassian.confluence.lifecycle] contextDestroyed Stopping Confluence
      2024-02-19 15:02:47,666 WARN [Catalina-utility-2] [confluence.impl.webapp.ContextShutdownThreadListener] logAndInterrupt Non-daemon thread [Thread-95] is still alive, and may be blocking clean shutdown - interrupting
      2024-02-19 15:02:47,666 WARN [Catalina-utility-2] [confluence.impl.webapp.ContextShutdownThreadListener] logAndInterrupt Non-daemon thread [pool-30-thread-1] is still alive, and may be blocking clean shutdown - interrupting 

      In our previous test, it took 5 mins for Confluence to be shut down completely.

       

      [2024-02-19 15:02:43] [info]  [ xxxx] Stopping service...
      [2024-02-19 15:07:47] [info]  [ xxxx] Service stop thread completed. 

       

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Suat Kandiş (Inactive)
            Votes:
            7 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: