| ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Monitoring Rule Execution Server Events > Finding the Cause of an Improper Rule Execution Server Configuration |
Finding the Cause of an Improper Rule Execution Server Configuration |
PREVIOUS NEXT |
Given the nature of log files it is sometimes not easy to establish the real cause of unexpected behavior from the Execution Unit (XU). It may be a bug, but the problem can also result from an improper XU configuration.
To help your investigation, use the shortest scenario or minimal application that raises the problem.
Then execute this application with the following settings:
traceLevel to ALL.
traceAutoFlush to true.
ruleset.trace.enabled to true.
ejb-jar.xml contained in jrules-bres-session-<app_server>.jar to change the traceEnabled property (on the stateless EJB). This property enables a trace mode to print the incoming message to a System.out:
If you are still not able to identify the cause of the error from the log messages, provide the following information to ILOG Customer Support:
| Note |
| If the issue seems to be a deadlock, the JVM thread dump of all threads may also be useful. |
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |