Review connector lifecyle

Details

  • User impact:
    Medium
  • Effort points:
    2
  • Similar Issues:
    None

Description

  • Connectors can send messages even when they are stopped, is that right/ok?
  • Dispatchers don't get stopped as part of connector stop() but rather only when connector is disposed.

These are just two things I came across there may be others....

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-4264 Connectors should check lifecycle and throw exception when attempts to send/dispatch/request are made on a stopped/stopping connector

  • 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.

Bug - A problem which impairs or prevents the functions of the product. MULE-4254 Some transport dispatchers send messages even when the connector has been stopped

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MULE-3533 Review and fix problems with life-cycle of major artifacts

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Patch submission - User code to be reviewed and incorporated into the product. MULE-3062 org.mule.providers.AbstractConnector allows connector to be disposed of multiple times.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MULE-4251 Connector workManager's should be disposed in stop phase before transport itself is stopped.

  • 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.

Task - A task that needs to be done. MULE-3111 Review life-cycle methods in agent/connector/service/component/objectfactory etc.

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MULE-2980 Connector lifecycle needs clarification

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment -

Dan, have you merged changes from the trunk? The last statement isn't true, this has been fixed.

Show
Andrew Perepelytsya added a comment - Dan, have you merged changes from the trunk? The last statement isn't true, this has been fixed.
Hide
Permalink
Daniel Feist added a comment -

I filed this issue a long time ago not recently. It seem Ross assigned it to himself but didnt update this issue after his work. Please update description and affect-version based on current behaviuor as you see it. Is the first one still an issue?

Show
Daniel Feist added a comment - I filed this issue a long time ago not recently. It seem Ross assigned it to himself but didnt update this issue after his work. Please update description and affect-version based on current behaviuor as you see it. Is the first one still an issue?

People

  • Assignee:
    Ross Mason
    Reporter:
    Daniel Feist
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: