[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: synapse-sample-700-site.diff synapse-sample-700-xml.diff Adding the fix for Sample 700 documentation [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_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-700-site.diff, synapse-sample-700-xml.diff, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_11.diff Hi , In the current MessageStore implementation there is no method to remove the message store from the synapse configuration. this patch will resolve that. thanks, Charith [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_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, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_9.diff Hi Hiranya, I added the MutiXML based configuration deploment for the DLC. Please have a look.And also i Message Store a synapse Artifact. [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_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, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_7.diff Added improvements to the current Persistence Message store [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, messagestore_patch_5.diff, messagestore_patch_6.diff, messagestore_patch_7.diff, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_7.diff Added improvements to the current Persistence Message store [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_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, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_6.diff Added the Java DoC improvements and a Sample guide to the Synapse Message store [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, messagestore_patch_5.diff, messagestore_patch_6.diff, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_5.diff This patch add the MessageStore serialization capability to synapse. [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, messagestore_patch_5.diff, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_4.diff synapse_sample_1.xml Attaching the patch for JMS Message store feature. and a test configuration file i used in my machine to test with this with ActiveMQ This patch will contain JMS Message store implementation Message serializer for Axis2MessageContext and SynapseMessage context. Due to the issue pointed out in https://issues.apache.org/jira/browse/SYNAPSE-673 JMS message store will be supported only with global level endpoints. I'll fix the above issue and improve this implementation in the future. [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, synapse_sample_1.xml, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_3.diff synapse_sample_1.xml Added the JMX view for the Message Store getSize() :int //give the current Message store size resendAll() : void //synapse will try to re-deliver all the Messages in the Message store. deleteAll(): void // delete all the Messages in Message store getMessageIds() : ListString //gives IDs of all messages stored in the MessageStore resend(String messageID) : void //try to re-deliver the Message with given ID delete(String messageID) : boolean //delete the Message with given id getEnvelope(String messageID) : SOAPEnvelope // get the SOAPEnvelope of the given Message ID And added the feature to put a Mediation sequence with the Message store.So when a message get stored in the store uses can point to a sequence to mediate. This will be useful with notification mechanisms. please review and commit [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 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_2.diff, messagestore_patch_3.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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: synapse_sample_1.xml messagestore_patch_1.diff This is the 1st patch for the Dead letter channel EIP implementation. This adds a in memory message store with a simple redelivery processor. Message store is currently associated with endpoints. This implemention will be improved with time as discussed in http://wiki.apache.org/general/charith/gsoc2010/synapse_deadLetter http://markmail.org/message/4lji7luz37k5xsv3?q=Synapse+Message+Store please review and commit [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 Project: Synapse Issue Type: New Feature Components: Core, Endpoints Reporter: Hiranya Jayathilaka Assignee: Hiranya Jayathilaka Fix For: FUTURE Attachments: messagestore_patch_1.diff, 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: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 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: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
