Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-31 Thread Rajika Kumarasiri
On Sun, Jan 31, 2010 at 12:27 PM, Supun Kamburugamuva supu...@gmail.comwrote: On Sun, Jan 31, 2010 at 11:10 AM, Hiranya Jayathilaka hiranya...@gmail.com wrote: Hi Rajika, On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri raj...@wso2.comwrote: hi, Right now in a failover scenario

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-31 Thread Hiranya Jayathilaka
Hi Rajika, Please see my comments inline. On Sun, Jan 31, 2010 at 3:37 PM, Rajika Kumarasiri raj...@wso2.com wrote: On Sun, Jan 31, 2010 at 12:27 PM, Supun Kamburugamuva supu...@gmail.comwrote: On Sun, Jan 31, 2010 at 11:10 AM, Hiranya Jayathilaka hiranya...@gmail.com wrote: Hi

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-31 Thread Ruwan Linton
On Sun, Jan 31, 2010 at 7:58 PM, Hiranya Jayathilaka hiranya...@gmail.comwrote: On Sun, Jan 31, 2010 at 6:07 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: I think think we should support hierarchical configuration, even for markForSuspension. When you configure a set of endpoints into a

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-31 Thread Hiranya Jayathilaka
On Mon, Feb 1, 2010 at 12:44 AM, Ruwan Linton ruwan.lin...@gmail.comwrote: On Sun, Jan 31, 2010 at 7:58 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: On Sun, Jan 31, 2010 at 6:07 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: I think think we should support hierarchical

Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-30 Thread Rajika Kumarasiri
hi, Right now in a failover scenario Synapse will try to re-send the message to the next available active endpoint ( this depend on the failover algorithm in use). For example if the 1st endpoint receives a timeout error or a connection refused error Synapse will try to send the message to the

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-30 Thread Ruwan Linton
+1, this model seems to be much clear. Thanks, Ruwan On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri raj...@wso2.com wrote: hi, Right now in a failover scenario Synapse will try to re-send the message to the next available active endpoint ( this depend on the failover algorithm in use).

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-30 Thread Hiranya Jayathilaka
Hi Rajika, On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri raj...@wso2.com wrote: hi, Right now in a failover scenario Synapse will try to re-send the message to the next available active endpoint ( this depend on the failover algorithm in use). For example if the 1st endpoint receives a

Re: Extending the endpoint configuration to handle the message in error situations (timeout, connection refused etc..) in a failover scenario

2010-01-30 Thread Supun Kamburugamuva
On Sun, Jan 31, 2010 at 11:10 AM, Hiranya Jayathilaka hiranya...@gmail.comwrote: Hi Rajika, On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri raj...@wso2.comwrote: hi, Right now in a failover scenario Synapse will try to re-send the message to the next available active endpoint ( this