An integration developer has implemented an error handling strategy for a mediation module as illustrated in the Exhibit. According to the strategy, if a runtime exception occurs during the invocation of the target service, the module must:
store a trace message in a file
store an error code in a DB error table
throw an exception in order to propagate the error to the invoking component
But at runtime the developer observes that when a runtime error occurs, no error code is written in the DB even if the fail primitive is executed.
What could be the most likely cause of the problem?
A. The 'Join transaction' qualifier of the 'JDBCImport' interface is set to True' while it must be set to 'False'.
B. The 'Transaction' qualifier of the 'ErrorHandlerMed' implementation is set to 'Global' while it must be set to 'Local'
C. The 'Join transaction' qualifier of the 'TargetServicelFPartner' interface is set to '' while it must be set to True'.
D. The 'Asynchronous invocation' qualifier of the 'JDBCImportPartner' reference is set to 'Commit' while it must be set to 'Call'.