synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charith Dhanushka Wickramarachchi (JIRA)" <>
Subject [jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
Date Mon, 27 Sep 2010 05:12:32 GMT


Charith Dhanushka Wickramarachchi updated SYNAPSE-618:

    Attachment: messagestore_patch_11.diff

added endpoint serialization for the attribute onFault = "message store name"

I saw the name attribute serialization code was repeated in several concrete classes . So
i bring that code to a upper level to reuse the code by introducing the method serializeCommonAttributes


> [GSoC] Implement a Dead Letter Channel for Synapse
> --------------------------------------------------
>                 Key: SYNAPSE-618
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Core, Endpoints
>            Reporter: Hiranya Jayathilaka
>            Assignee: Hiranya Jayathilaka
>             Fix For: FUTURE
>         Attachments: messagestore_patch_1.diff, messagestore_patch_10.diff, messagestore_patch_11.diff,
messagestore_patch_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, messagestore_patch_5.diff,
messagestore_patch_6.diff, messagestore_patch_7.diff, messagestore_patch_7.diff, messagestore_patch_8.diff,
messagestore_patch_9.diff, synapse_sample_1.xml, synapse_sample_1.xml, synapse_sample_1.xml,
> Currently when Synapse attempts to send a message and if it fails, following actions
can be configured to deal with the error:
> * Execute a fault sequence and handle the failed request gracefully
> * Fail-over to a different endpoint
> In addition to these, Synapse ESB should support the "dead letter channel" enterprise
integration pattern to deal with various errors that might occur during mediation or while
sending. With the dead letter channel, the failed message will be put into a message store
in the ESB. Later the ESB can retry to send the messages in the message store. 
> We should be able to have multiple implementations of the actual message store and should
be able to configure which store to use for a particular scenario. Users should be able to
implement their own message stores and plug into the ESB easily. To start with we can have
a simple in-memory message store and a persisting store based on JDBC or JMS. 
> References:
> Possible Mentors:
> Hiranya Jayathilaka

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message