Hi Malaka, I did already try this, in the FaultSequence I created a message with the PayloadFactory (or the Fault mediator) but it can only be sent directly to the client. I need it to go to the aggregation step and be aggregated before it is sent to the client.
Kind regards, Koen From: Malaka Silva [mailto:mal...@wso2.com] Sent: vrijdag 13 februari 2015 9:56 To: Koen Geerts Cc: dev@wso2.org Subject: Re: [Dev] [ESB] Scatter-Gather with error handling Hi Koen, Please use PayloadFactory Mediator to generate the required payload (Error Message) in fault sequence. [1] [1] https://docs.wso2.com/display/ESB481/PayloadFactory+Mediator On Fri, Feb 13, 2015 at 1:10 PM, Koen Geerts <koen.gee...@intrion.com<mailto:koen.gee...@intrion.com>> wrote: Hi, I have a question on an ESB proxy/sequence. I will do my best describing the problem and the issues I'm facing: Let's assume that for this case we have 1 ESB and 2 AS. The AS are copies of each other. They provide load-balancing/ High availability. On the ESB we have one proxy which will call endpoints on the AS. ESB proxy | |-sequence | |-- EP1 --( o-- AS1 | |-- EP2 --( o-- AS2 It is important that following constraints are met at all times: - 1 invocation of a soap method on the ESB will result in 1 invocation on each AS (given they're up and running) - When both servers return a valid response (Not soap fault), one of the two responses should be the ESB response - When one of the two AS returns an error/fault, the response from the ESB proxy should be this error/fault - When one of the two AS is down, we should invoke the endpoint that is still alive and the response (valid or fault) should be the response of the ESB proxy. The setup highly resembles the Scatter-Gather EIP; we have one request, we scatter it over our AS endpoints, we gather the responses and based on some rules we determine the ESB response. We just lack a solution to handle the error that occurs when an endpoint is down. I already configured multiple ESB sequences to try to make this happen as it should. The problem is that when an endpoint is down, we get a "could not connect to back end" error, as expected. This error can only be handled in the fault sequence. We cannot receive the soap fault into our gather step to cope with it. Is there a way to achieve this? How do you advise on configuring this? Kind Regards, Koen Geerts _______________________________________________ Dev mailing list Dev@wso2.org<mailto:Dev@wso2.org> http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/> Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary.
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
