Need to support the graceful shutdown feature.

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.0.1
  • Fix Version/s: 2.2.4 (EE only)
  • Component/s: Core: (other)
  • Labels:
    None
  • Environment:

    Mule 2.0.1 on any platforms

  • User impact:
    Medium
  • Similar Issues:
    None

Description

Graceful shutdown. It is required to allow Mule services get shutdown gracefully. That is, when a Mule server is instructed to shutdown, all in-flight message processing and transactions should be completed before Mule services become unavailable; while new messages stop to be processed, new requests rejected with proper responses.

This is a must feature requested by one of the biggest Mule customer.

Issue Links

blocks

Improvement - An improvement or enhancement to an existing feature or task. MULE-3688 Graceful/Forceful shutdown with timeouts

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment -

Descoping since it is tracked by EE-606

Show
Ross Mason added a comment - Descoping since it is tracked by EE-606
Hide
Permalink
r h added a comment -

I have previously raised this as an issue in the mule forum http://forums.mulesoft.org/message.jspa?messageID=5160

unfortunately we found the current solution unsuitable so we have applied a change to our system which scans each service in a tree like manner shutting them down when a service has no inbound events and is in a stale state i.e. no outbound messages for a while.

this is less than ideal, an approach where we could have used the notifications and blocked the services thread might have been slightly better. but still not ideal

Show
r h added a comment - I have previously raised this as an issue in the mule forum http://forums.mulesoft.org/message.jspa?messageID=5160 unfortunately we found the current solution unsuitable so we have applied a change to our system which scans each service in a tree like manner shutting them down when a service has no inbound events and is in a stale state i.e. no outbound messages for a while. this is less than ideal, an approach where we could have used the notifications and blocked the services thread might have been slightly better. but still not ideal
Hide
Permalink
r h added a comment -

is this going to be backported to the CE edition if it is changed in the EE edition

Show
r h added a comment - is this going to be backported to the CE edition if it is changed in the EE edition

People

  • Assignee:
    Daniel Feist
    Reporter:
    Weiwei Hsieh
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: