Lingo
  1. Lingo
  2. LINGO-44

MultiplexingRequestor leaves lingering threads after close() called

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.3
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      ActiveMQ 4.1.1, Windows XP
    • Patch Submitted:
      Yes
    • Number of attachments :
      1

      Description

      The MultiplexingRequestor class does not have a close() method to close the ScheduledThreadPoolExecutor. This leaves non-daemon threads hanging around and thus applications will not quit until System.exit() is called (causing Tomcat applications exporting Lingo services and standard Java apps calling Lingo services to hang forever on shutdown).

      Attached is an updated MultiplexingRequestor class that fixes the issue.

        Activity

        No changes have yet been made on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Jason Koch
          • Votes:
            3 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 30 minutes
              30m
              Remaining:
              Remaining Estimate - 30 minutes
              30m
              Logged:
              Time Spent - Not Specified
              Not Specified