For a certain ruleset, no trace is logged in DW, and no records can be found in EXEUTION_TRACES table of DW database.
Server logs do not contain any messages about the execution traces for this ruleset.
The issue reproduces only for this project. For other projects deployed in RES, traces are being logged in DW. Also, the same project generates execution traces in other environments.
The following properties have been set:
monitoring.enabled = true
monitoring.filters = INFO_EXECUTION_DATE=true,INFO_EXECUTION_DURATION=true,INFO_TOTAL_TASKS_EXECUTED=true,INFO_TOTAL_RULES_NOT_FIRED=true,INFO_EXECUTION_EVENTS=true,INFO_TOTAL_TASKS_NOT_EXECUTED=true,INFO_TOTAL_RULES_FIRED=true,INFO_RULESET_PROPERTIES=true
ruleset.bom.enabled = false (for true value, the problem still occurs)
ruleset.sequential.trace.enabled = true
ruleset.trace.enabled = true
How can I diagnose this issue?
Answer by Miriam.Kaestner (8892) | Mar 17, 2016 at 06:47 AM
To minimize the impact of Decision Warehouse (DW) monitoring on the processing of ruleset executions, possible failures to save the trace to the database may remain silent (no stack trace in the logs of the application server).
If an issue arises during DW trace persistence at runtime, the related messages and stack traces are only available programmatically through the following API:
ilog.rules.res.session.IlrSessionResponse.getWarnings()
You can obtain additional debug information using the diagnostic tool jrules-debugtrace.jar
Can we create a stored procedure in RES schema to purge the Decison Warehouse traces? 1 Answer
RES log shows NoAccessRuntimeException on Resource IlrXUManagement 1 Answer
What is the best practice to upgrade RES from v7.1 to v8.8? 2 Answers
Unable to capture Decision Traces 1 Answer
When to use libraries jrules-res-execution.jar and jrules-res-session-java.jar 1 Answer