Mule
  1. Mule
  2. MULE-3559

Ensure that all message receiver implementations clean up after themselves on exceptions and close any input streams

    Details

    • User impact:
      Low
    • Effort points:
      1
    • Similar Issues:
      MULE-2591InputStreams not closed after streaming response
      MULE-2499No way to close streams (and release connections) if an exception occurs outside of the MessageDispatcher
      MULE-3065Review all transformers for streaming compatibility
      MULE-4556Stream is closed too early when request message fails authorization
      MULE-1883Streaming model interceptor and exception strategies not behaving as expected.
      MULE-2617Clean up the ConfigurationBuilder interface
      MULE-1242Non-materializing streaming receiver for TCP
      MULE-5269Clean up exception strategy schema elements after exception strategy work in core
      MULE-6533File stream closed before catch-exception-strategy is called
      MULE-534Tcp Streaming Message Receiver based on PollingMessageReceiver

      Issue Links

        Activity

        Hide
        Steven Camina added a comment -

        Closing this issue because it affects a very old version of Mule. Please reopen if this is an issue.

        Show
        Steven Camina added a comment - Closing this issue because it affects a very old version of Mule. Please reopen if this is an issue.

          People

          • Assignee:
            Steven Camina
            Reporter:
            Daniel Feist
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development