SAM not logging FAULT_IN event when a service call fails in tESBConsumer


Sometimes, if tESBConsumer receives a fault response because it fails to call a web service provider, the SAM (Service Activity Monitoring) doesn't add a FAULT_IN event to its database. Is this expected?


This is expected behavior if the service provider is not available.

  • There will be a FAULT_IN event only for Business Faults. For example, the consumer sends a request with empty/wrong parameters, and the service provider sends a Fault as a response.

  • There will not be a FAULT_IN event if a service provider is not available (it cannot generate a FAULT_IN event, because this service is not available).

So, the only way to get a FAULT_IN event in the SAM database is to enable the SAM feature for the service consumer.

Version history
Revision #:
3 of 3
Last update:
‎09-29-2018 12:12 AM
Updated by:
Labels (4)