Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-564

CommonsHttpMessageSender no longer properly shuts down MultiThreadedHttpConnectionManager

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.9
    • Component/s: None
    • Labels:
      None

      Description

      As of revision 1414 of CommonsHttpMessageSender, the MultiThreadedHttpConnectionManager never gets it's shutdown method invoked.

      It appears that the prior revision of CommonsHttpMessageSender implemented DisposableBean, and invoked this properly.
      SWS-482 removed the destroy method to cope with a problem report, but the result is worse.

      If you use MultiThreadedHttpConnectionManager, you have to call it's shutdown method, or it will block application exit.
      For example, I have a class with a main method that uses WebServiceTemplate along with CommonsHttpMessageSender that is invoked via an ant task. The main method will complete, but the JVM cannot exit.

      Lets revisit SWS-482 and come up with a means for resolving the issue appropriately.
      The reporter of that issue mentions that:
      "it happens it is always after we redeploy our application (weblogic 9.2MP2)".

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          61d 17h 15m 1 Arjen Poutsma 09/Nov/09 8:37 PM
          In Progress In Progress Resolved Resolved
          4h 9m 1 Arjen Poutsma 10/Nov/09 12:47 AM
          Resolved Resolved Closed Closed
          906d 6h 15m 1 Arjen Poutsma 04/May/12 7:03 AM

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              nblair Nicholas Blair
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 4h 5m
                4h 5m