ICEfaces
  1. ICEfaces
  2. ICE-5134

RequestManager stuck thread keeps Tomcat 6 from shutting down

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.2
          • Fix Version/s: 1.8.3
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces Core, ICEfaces Push Server
          • Workaround Exists:
            Yes
          • Workaround Description:
            Use the [tomcat-home]/bin/catalina.sh shell script and CTRL+C to startup and shutdown the Tomcat server when using log level DEBUG.

            Description

            RequestManager spawns a non daemon thread at log level DEBUG that is never shutdown, preventing Tomcat 6 from shutting down when using [tomcat-home]/bin/startup.sh and [tomcat-home]/bin/shutdown.sh shell scripts to start and stop the Tomcat server.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              Changed Fix Version(s) to 1.8.3

              Show
              Jack Van Ooststroom added a comment - Changed Fix Version(s) to 1.8.3
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              The RequestManager contains DEBUG level logging that uses a thread to print out the list of pending requests every so often. The created thread to do this however was not a daemon thread, causing it to linger on even after Tomcat shutdown. The RequestManager now uses the general ScheduledThreadPoolExecutor to execute this logging task. This executor is being properly shutdown upon Servlet destroy, Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - The RequestManager contains DEBUG level logging that uses a thread to print out the list of pending requests every so often. The created thread to do this however was not a daemon thread, causing it to linger on even after Tomcat shutdown. The RequestManager now uses the general ScheduledThreadPoolExecutor to execute this logging task. This executor is being properly shutdown upon Servlet destroy, Marking this one as FIXED.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Jack Van Ooststroom
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: