| ILOG JRules User Guide > Running and Debugging > Tasks > Troubleshooting Execution > Handling Exceptions in Generated Bytecode |
Handling Exceptions in Generated Bytecode |
PREVIOUS NEXT |
If you have an exception during execution with a stack trace beginning with ilog.rules.engine.sequential.generated, it indicates that an execution occurs within generated bytecode. Bytecode is generated when using the sequential or Fastpath modes, or the RetePlus with useJit enabled.
The characters following ilog.rules.engine.sequential.generated indicate which part of the IRL code caused the exception. It may be the action part of a rule, or a function. In this last case, the function word will be present before the function name. If the function name begins with translation, then it means the function has been generated by the BOM to XOM mapping. The function content is the body of a mapping of a business class member whose name follows the translation word.
For example, if a stack trace begins with:
java.lang.NullPointerException
at
ilog.rules.engine.sequential.generated.loanvalidation$35$$33$$_$validation_0.function_translation_loan_LoanUtil_getStringSize(ilog.rules.engine.sequential.generated.loanvalidation$35$$33$$_$validation_0)
It indicates that a null pointer exception occurred in the body of the mapping of the business method loan.LoanUtil.getStringSize. To avoid this exception, you will have to check for nulls in the body.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |