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

On Sun, Jan 31, 2010 at 11:10 AM, Hiranya Jayathilaka wrote: > Hi Rajika, > > On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri 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 >> alg

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #314

See -- [...truncated 2662 lines...] [Fatal Error] :-1:-1: Premature end of file. org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.in

Re: Disabling the tests which are failing

Actually the recent builds have succeeded, but fails due to some problem in Hudson: [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Synapse

Re: Disabling the tests which are failing

On Sat, Jan 30, 2010 at 8:40 PM, Ruwan Linton wrote: > Devs, > > The failing tests of the synapse transports build seems to be failing due > to issues in the test framework. I am going to disable these tests and the > Script mediator test as well since it is breaking on JDK 1.6, till we find > the

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

Hi Rajika, On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri 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 timeout erro

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

+1, this model seems to be much clear. Thanks, Ruwan On Sun, Jan 31, 2010 at 9:31 AM, Rajika Kumarasiri 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

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

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 next

Hudson build is unstable: Synapse - 1.3 - SNAPSHOT #313

See - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org

Hudson build is still unstable: Synapse - 1.3 - SNAPSHO T » Apache Synapse - Non-blocking HTTP/s Transport #313

See - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #312

See -- [...truncated 4159 lines...] [INFO] Installing

Disabling the tests which are failing

Devs, The failing tests of the synapse transports build seems to be failing due to issues in the test framework. I am going to disable these tests and the Script mediator test as well since it is breaking on JDK 1.6, till we find the proper fix for those. Thanks, Ruwan -- Ruwan Linton Technical