Create and enforce simple, yet correct UMOMessage synchronization rules

Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

The current way of handling acess to the current event's message is less than properly defined; in some places access is synchronized (sometimes for no apparent reason?!), in others it is not. While the most pressing concurrency issues from 1.2 have been solved and the situation has definitely improved, I'm not entirely sure we have done it correctly and just enjoy "accidental success" for the moment.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-893 Clarify/reachitect MuleMessage property mutability & handling

  • 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-891 Plan roadmap to 2.0 via 1.3.x, 1.4.x

  • Major - Major loss of function.
  • 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 -

Descoping the 1.4.1, unset Fix Version for some issues.

Show
Andrew Perepelytsya added a comment - Descoping the 1.4.1, unset Fix Version for some issues.
Hide
Permalink
Daniel Feist added a comment -

We are still just about getting by with "accidental success" but this still does need to be tackled.

Show
Daniel Feist added a comment - We are still just about getting by with "accidental success" but this still does need to be tackled.

People

  • Assignee:
    Unassigned
    Reporter:
    Holger Hoffstaette
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: