[
https://issues.apache.org/jira/browse/SYNAPSE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307127#comment-15307127
]
Hudson commented on SYNAPSE-1020:
---------------------------------
SUCCESS: Integrated in Synapse - Trunk #5257 (See
[https://builds.apache.org/job/Synapse%20-%20Trunk/5257/])
Implementing deactivate sequence for forwarding jobs; Applied patch from
SYNAPSE-1020 (hiranya: rev 1746209)
*
java/modules/core/src/main/java/org/apache/synapse/message/processors/forward/ForwardingJob.java
*
java/modules/core/src/main/java/org/apache/synapse/message/processors/forward/ForwardingProcessorConstants.java
> Deactivate sequence for message processor auto deactivations
> ------------------------------------------------------------
>
> Key: SYNAPSE-1020
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1020
> Project: Synapse
> Issue Type: Bug
> Reporter: prabath ariyarathna
> Assignee: Hiranya Jayathilaka
> Fix For: 3.0
>
> Attachments: deactivete_seq.diff
>
>
> The deactivate sequence that will be executed when the processor is
> deactivated automatically. Automatic deactivation occurs when the maximum
> delivery attempts is exceeded.
> Since we cannot automatically activate message processor after it was
> deactivated. In some scenarios, we need to get some actions for the message
> processor deactivations(Eg: Notify via email/sms to the relevant parties
> when message processor getting deactivated). So we can use this sequence for
> achieving this type of requirements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
