Hi Team,
A customer wants to know when exactly the Step defined in FaultRule of TargetEndpoint executed.
The error called ‘TargetError’ is invoked by the condition where , is not reachable. So the error message log we see is:
ERROR HTTP.CLIENT - HTTPClient$Context.onConnectFailure() : connect to null failed with exception {}
java.lang.RuntimeException: Host not reachable
And a has a MessageLogging policy called ‘LoggingResponse’.
Then we see the following 3 cases of the sequence of execution as it’s recorded on Trace log:
- case-1: TargetError > Staring PostClientFlow> LoggingResponse
- case-2: Staring PostClientFlow > TargetError > LoggingResponse
- case-3: Staring PostClientFlow > LoggingResponse > TargetError
So we see that ‘TargetError’ appears in one of the above 3 positions in the flows.
Is this by design or anything wrong with this behavior?
Someone please give us advices.
Regards,
Toshi