[overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051338#comment-13051338 ] 

Gary Brown commented on RTGOV-645:
----------------------------------

Hi Michael - thanks for the additional information.

It might be best to take one point at a time - so firstly want to concentrate on the resubmission failure and what could occur.

In your description I believe there is an assumption that failure of a resubmission will result in a single further situation - and therefore if this was the case, your description of only the 'newest' situation being resubmitted again makes sense. However what happens if when the resubmitted message fails it results in multiple further situations being created? And due to the async nature of the system, there is no guarantee in which order these new situations would be created?


> Resubmitted message should identify source situation to enable further failures (situations) to be linked back
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-645
>                 URL: https://issues.jboss.org/browse/RTGOV-645
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.2.0
>
>
> When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events.
> If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)