synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Weerasiri (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
Date Wed, 17 Mar 2010 19:13:27 GMT


Denis Weerasiri commented on SYNAPSE-618:

Hi devs,
I am Denis Weerasiri, a final year student from University of Moratuwa, Sri Lanka. I am hoping
to participate in GSOC 2010 program. This would be my second GSOC. Last year I worked in and
successfully completed Apache ODE project titled "Web-based BPEL debugger for Apache ODE".

I would be willing to work on Apache Synapse project, under this idea. I have experience in
developing applications with ESB, axis2, ODE etc. But upto now I'm still reading the code
and documentation, and trying to understand implementing a message store. 
Is there any other specific areas, I should consider regarding this to get a correct overall
view of the project?

Best Regards,
Denis Weerasiri.

[1] -

> [GSoC] Implement a Dead Letter Channel for Synapse
> --------------------------------------------------
>                 Key: SYNAPSE-618
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Core, Endpoints
>            Reporter: Hiranya Jayathilaka
>             Fix For: FUTURE
> 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