JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-3559

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

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 2.0.1
  • Fix Version/s: Tech. Debt
  • Component/s: Core: Exception Handling, Core: Streaming
  • Labels:
    None
  • User impact:
    Low
  • Effort points:
    1
  • Similar Issues:
    None

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-2499 No way to close streams (and release connections) if an exception occurs outside of the MessageDispatcher

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Daniel Feist
Vote (0)
Watch (0)

Dates

  • Created:
    16/Jul/08 08:58 PM
    Updated:
    30/Nov/08 06:17 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.