synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afkham Azeez" <afk...@gmail.com>
Subject Re: errorHandler not invoked when an application node fails
Date Thu, 12 Jun 2008 11:45:32 GMT
I'm creating an AddressEndpoint and sending the message now, and everything
seems to be working fine.

Thanks
Azeez

On Thu, Jun 12, 2008 at 1:34 PM, Ruwan Linton <ruwan.linton@gmail.com>
wrote:

> Hi Azeez,
>
> I have tested the fault handling of synapse and found that it is working
> fine, and then I tried the exact configuration that you sent with a bogus
> address endpoint instead of the intelligentLoadbalance. When I run this, it
> worked and the fault handler got invoked.
>
> Can you please recheck this.
>
> Thanks,
> Ruwan
>
>
> On Thu, Jun 12, 2008 at 12:16 PM, Afkham Azeez <afkham@gmail.com> wrote:
>
>> While testing my load balancer implementation, I killed an application
>> node just to see what happens. Apparently, the load balancer tries to
>> forward the request to the failed node and detects that this node has
>> failed. However, the Axis2 client that invoked synapse does not get a
>> response, and simply times out. Looks like the error handler sequence is not
>> getting invoked. The relevant configuration section looks like this:
>>
>>
>> ----------------------------------------------------------------------------------------------------------------------------------------------
>> <sequence name="main" onError="errorHandler">
>>         <in>
>>             <send>
>>                 <endpoint>
>>                     <intelligentLoadbalance/>
>>                 </endpoint>
>>             </send>
>>             <!--drop/-->
>>         </in>
>>
>>         <out>
>>             <!-- Send the messages where they have been sent (i.e.
>> implicit To EPR) -->
>>             <send/>
>>         </out>
>>     </sequence>
>>     <sequence name="errorHandler">
>>         <makefault>
>>             <code value="tns:Receiver" xmlns:tns="
>> http://www.w3.org/2003/05/soap-envelope"/>
>>             <reason value="COULDN'T SEND THE MESSAGE TO THE SERVER."/>
>>         </makefault>
>>         <header name="To" action="remove"/>
>>         <property name="RESPONSE" value="true"/>
>>         <send/>
>> </sequence>
>>
>> ---------------------------------------------------------------------------------------------------------------------------------------------
>>
>> At the end of the log, I'm seeing the following printed:
>>
>>  INFO LogMediator To: http://10.100.1.52:9763/wsas/services/Calculator,
>> WSAction: urn:add, SOAPAction: urn:add, MessageID:
>> urn:uuid:08B30E45863D8110F81213252716695, Direction: request, MESSAGE =
>> Executing default "fault" sequence, ERROR_CODE = 00000, ERROR_MESSAGE =
>> java.net.ConnectException: Connection refused, Envelope: <?xml version='1.0'
>> encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="
>> http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns1:add
>> xmlns:ns1="http://clustering.wso2.org
>> "><ns1:a>13226</ns1:a><ns1:b>5665</ns1:b><ns1:context>ConfigurationContext</ns1:context></ns1:add></soapenv:Body></soapenv:Envelope>
>>
>> Any idea what can be wrong? Is there an error in the synapse configuration
>> I've provided?
>>
>> --
>> Thanks
>> Afkham Azeez
>>
>> http://afkham.org
>> http://www.wso2.org
>> GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"




-- 
Thanks
Afkham Azeez

http://afkham.org
http://www.wso2.org
GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760

Mime
View raw message