Hi Roberto > 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. > Ah.. I get your point now! No, Synapse doesn't look at the message and mark the endpoint as failed.. this is a good suggestion for improvement though.. Let me see what can be done
cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
