Thanks. The problem is that when I'm trying to access to an inactive
endpoint I don't obtain an error code in the 101XXX error codes list. I
obtain a SOAP fault like this from Axis2 on the remote machine:
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>The system is attempting to access an inactive service:
....</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
that isn't interpreted like an error from Synapse. For this reason, the
suspension never happens.I think the problem is that in Syanpse failover
configuration there is no possibility to recognize a soap fault in order to
manage endpoint suspension.
Thanks in advance.
2010/1/14 Asankha C. Perera <[email protected]>
> Hi Roberto
> > Hi all, I'd like to make the failover endpoint configuration working not
> > only when one of the servers is shut down but even if one of the
> endpoints
> > is inactive
> First of all, it seems like you've not yet subscribed to the user list
> to post messages.. So copying this to you directly
>
> An endpoint becomes suspended when its known to be down. A timeout or
> intermittent error marks it for suspension, and on exceeding the retry
> count in this state, it makes the endpoint suspended. You can configure
> the error codes on which an endpoint is marked for timeout and
> suspension, so if you change the default and make a timeout a suspension
> error you will get exactly what you want - although that may not be the
> correct solution
>
> cheers
> asankha
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
>
