Re: [VOTE] Release Synapse-2.0.0 (Take2)
Hi , Sorry if i m too late. I ran few tests with the synapse samples and Found a issue with the Sample 700 (Synapse Message Store). The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent from the patch i attached in [2] I think its because that patch was given for the new synapse xml schema and getting it back to the old schema again caused this error. Current synapse_sample_700.xml does not work since global endpoint definition and sequence definition is in side the main sequence. I'm attaching the current version of the synapse_sample_700.xml with this mail. [1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/ [2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff thanks, Charith On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Folks, sorry to let you know that the build is taking another day, as the source pack building issue is still there. Trying to figure out what was wrong, some times on a clean repo the build gets the same exception of a corrupted jar but is not really corrupted. Thanks, Ruwan On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Hi Eric, On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric eric.hub...@foxmobile.comwrote: Doing the mediator API related changes I asked myself whether concrete mediators like FaultMediator should really widen the visibility of AbstractMediatorFactory#createSpecificMediator. At least some of Synapse built-in mediators change the visibility from protected to public. I did not check all of them. I don’t think this is generally a good idea as to my understanding “users” of any MediatorFactory implementation should always only call createMediator (which internally delegates to createSpecificMediator). Otherwise functionality from the AbstractMediatorFactory might be mistakenly bypassed. Of course that is the design, some how by mistake they left as public and now I have fixed that. Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc has not been adjusted to the added parameter “Properties” which use is still unclear to me. Added properties param to the JavaDoc. Thanks, Ruwan Apart from that I have positive feedback regarding my tests with simple mediation and usage of the nhttp transports. I could not spot any problem so far. I also did a couple of small load tests against one small instance reaching about 2500 requests per second and letting it run on that level for a few hours. Regards, Eric -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Sunday, December 12, 2010 3:33 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hi Eric, On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: I found another issue with the nhttp transports: I guess Synapse 2.0 release should not be shipped with http core / http core nio 4.1 alpha 1 dependencies, but the final release version 4.1. I also think the patch for httpcore-193 is no longer needed and the binary patch should not be in the patches directory. Cool, I guess a good catch, will fix it. Apart from that I finished the mediator migration and I’m now starting to test including custom mediators. Unfortunately I will have to continue tomorrow, as I have to take care of other things today. Sure no problem. Regards, Eric PS: Is there already an updated version of the migration tool to test? Unfortunately not yet Eric, I didn't have time to work on that, planning to work on resolving all the issue today starting from now on. :-) Will post the tool once there is an update. Thanks, Ruwan -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Thursday, December 09, 2010 11:08 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hiranya, I've fixed this dependency issue, I expect you to do a build on the local machine and check this, will wait for your comments to the next RC :-) Thanks, Ruwan On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka hiranya...@gmail.com wrote: I hate to be a PITA but I see another issue with this. The FIX transport has been included in the latest binary. So that's good. But I can see that Quickfix/J has also crept into the distro (about 9MB). FIX transport also requires MINA and SLF4J which are not included in the binary. So IMO either we should include all the required dependencies or none of them. I think we should add an exclusion to Quickfix/J and keep it out of the binary. WDYT? Thanks, Hiranya On Wed, Dec 8, 2010 at 12:27 PM, Ruwan Linton ruwan.lin...@gmail.com wrote: Hi Devs, This is take 2 call for votes to release Synapse-2.0.0. Please review
[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
Re: [VOTE] Release Synapse-2.0.0 (Take2)
Hi, I have attached the patches for fix this problem to [1] patch to fix the problem with the sites sample documentation can be found at[2] and changes to the sample 700 configuration file can be found at [3] [1]https://issues.apache.org/jira/browse/SYNAPSE-618 [2] https://issues.apache.org/jira/secure/attachment/12466572/synapse-sample-700-site.diff [3] https://issues.apache.org/jira/secure/attachment/12466571/synapse-sample-700-xml.diff thanks, Charith On Sun, Dec 19, 2010 at 6:27 PM, Charith Wickramarachchi charith.dhanus...@gmail.com wrote: Hi , Sorry if i m too late. I ran few tests with the synapse samples and Found a issue with the Sample 700 (Synapse Message Store). The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent from the patch i attached in [2] I think its because that patch was given for the new synapse xml schema and getting it back to the old schema again caused this error. Current synapse_sample_700.xml does not work since global endpoint definition and sequence definition is in side the main sequence. I'm attaching the current version of the synapse_sample_700.xml with this mail. [1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/ [2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff thanks, Charith On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Folks, sorry to let you know that the build is taking another day, as the source pack building issue is still there. Trying to figure out what was wrong, some times on a clean repo the build gets the same exception of a corrupted jar but is not really corrupted. Thanks, Ruwan On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Hi Eric, On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: Doing the mediator API related changes I asked myself whether concrete mediators like FaultMediator should really widen the visibility of AbstractMediatorFactory#createSpecificMediator. At least some of Synapse built-in mediators change the visibility from protected to public. I did not check all of them. I don’t think this is generally a good idea as to my understanding “users” of any MediatorFactory implementation should always only call createMediator (which internally delegates to createSpecificMediator). Otherwise functionality from the AbstractMediatorFactory might be mistakenly bypassed. Of course that is the design, some how by mistake they left as public and now I have fixed that. Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc has not been adjusted to the added parameter “Properties” which use is still unclear to me. Added properties param to the JavaDoc. Thanks, Ruwan Apart from that I have positive feedback regarding my tests with simple mediation and usage of the nhttp transports. I could not spot any problem so far. I also did a couple of small load tests against one small instance reaching about 2500 requests per second and letting it run on that level for a few hours. Regards, Eric -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Sunday, December 12, 2010 3:33 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hi Eric, On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: I found another issue with the nhttp transports: I guess Synapse 2.0 release should not be shipped with http core / http core nio 4.1 alpha 1 dependencies, but the final release version 4.1. I also think the patch for httpcore-193 is no longer needed and the binary patch should not be in the patches directory. Cool, I guess a good catch, will fix it. Apart from that I finished the mediator migration and I’m now starting to test including custom mediators. Unfortunately I will have to continue tomorrow, as I have to take care of other things today. Sure no problem. Regards, Eric PS: Is there already an updated version of the migration tool to test? Unfortunately not yet Eric, I didn't have time to work on that, planning to work on resolving all the issue today starting from now on. :-) Will post the tool once there is an update. Thanks, Ruwan -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Thursday, December 09, 2010 11:08 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hiranya, I've fixed this dependency issue, I expect you to do a build on the local machine and check this, will wait for your comments to the next RC :-) Thanks, Ruwan On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka hiranya...@gmail.com wrote: I hate to be a PITA but I see another issue with this.
Re: [VOTE] Release Synapse-2.0.0 (Take2)
Hi Charith, Thanks a lot and it is not too late. :-) will get this path into the 2.0 branch. Thanks, Ruwan On Sun, Dec 19, 2010 at 6:50 PM, Charith Wickramarachchi charith.dhanus...@gmail.com wrote: Hi, I have attached the patches for fix this problem to [1] patch to fix the problem with the sites sample documentation can be found at[2] and changes to the sample 700 configuration file can be found at [3] [1]https://issues.apache.org/jira/browse/SYNAPSE-618 [2] https://issues.apache.org/jira/secure/attachment/12466572/synapse-sample-700-site.diff [3] https://issues.apache.org/jira/secure/attachment/12466571/synapse-sample-700-xml.diff thanks, Charith On Sun, Dec 19, 2010 at 6:27 PM, Charith Wickramarachchi charith.dhanus...@gmail.com wrote: Hi , Sorry if i m too late. I ran few tests with the synapse samples and Found a issue with the Sample 700 (Synapse Message Store). The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent from the patch i attached in [2] I think its because that patch was given for the new synapse xml schema and getting it back to the old schema again caused this error. Current synapse_sample_700.xml does not work since global endpoint definition and sequence definition is in side the main sequence. I'm attaching the current version of the synapse_sample_700.xml with this mail. [1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/ [2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff thanks, Charith On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Folks, sorry to let you know that the build is taking another day, as the source pack building issue is still there. Trying to figure out what was wrong, some times on a clean repo the build gets the same exception of a corrupted jar but is not really corrupted. Thanks, Ruwan On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Hi Eric, On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: Doing the mediator API related changes I asked myself whether concrete mediators like FaultMediator should really widen the visibility of AbstractMediatorFactory#createSpecificMediator. At least some of Synapse built-in mediators change the visibility from protected to public. I did not check all of them. I don’t think this is generally a good idea as to my understanding “users” of any MediatorFactory implementation should always only call createMediator (which internally delegates to createSpecificMediator). Otherwise functionality from the AbstractMediatorFactory might be mistakenly bypassed. Of course that is the design, some how by mistake they left as public and now I have fixed that. Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc has not been adjusted to the added parameter “Properties” which use is still unclear to me. Added properties param to the JavaDoc. Thanks, Ruwan Apart from that I have positive feedback regarding my tests with simple mediation and usage of the nhttp transports. I could not spot any problem so far. I also did a couple of small load tests against one small instance reaching about 2500 requests per second and letting it run on that level for a few hours. Regards, Eric -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Sunday, December 12, 2010 3:33 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hi Eric, On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: I found another issue with the nhttp transports: I guess Synapse 2.0 release should not be shipped with http core / http core nio 4.1 alpha 1 dependencies, but the final release version 4.1. I also think the patch for httpcore-193 is no longer needed and the binary patch should not be in the patches directory. Cool, I guess a good catch, will fix it. Apart from that I finished the mediator migration and I’m now starting to test including custom mediators. Unfortunately I will have to continue tomorrow, as I have to take care of other things today. Sure no problem. Regards, Eric PS: Is there already an updated version of the migration tool to test? Unfortunately not yet Eric, I didn't have time to work on that, planning to work on resolving all the issue today starting from now on. :-) Will post the tool once there is an update. Thanks, Ruwan -- *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com] *Sent:* Thursday, December 09, 2010 11:08 AM *To:* dev@synapse.apache.org *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2) Hiranya, I've fixed this dependency issue, I expect you to do a build on the local machine and
