You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2016/05/31 02:05:13 UTC
[jira] [Resolved] (SYNAPSE-1020) Deactivate sequence for message
processor auto deactivations
[ https://issues.apache.org/jira/browse/SYNAPSE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka resolved SYNAPSE-1020.
------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0
Patch applied
> 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-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org