Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
How to troubleshoot runtime exception errors in Configuration — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

How to troubleshoot runtime exception errors in Configuration

Received Response
12
Views
2
Comments
edited Jan 12, 2021 4:57PM in Configure Price Quote 2 comments

Summary

Based on data in the error log, how do you identify the rule that is triggering the runtime exception error?

Content

When I encounter a RuntimeException error, the first place I look for information is the Error Logs (bm.log).  The logs will often provide me with an ID like the example below:

12 Jan 2021 11:50:39,473 [ERROR] com.bm.xchange.rest.exceptions.BMSystemExceptionHandler.toResponse(BMSystemExceptionHandler.java:48) - System exception
com.bm.xchange.services.scripts.bmjscript.BMJScriptSystemException: A RuntimeException has occurred.
    at com.bm.xchange.bmscript.configuration.action.ConfigRuleAction_1471537219.exec(ConfigRuleAction_1471537219.java:95) ~[?:?]

My understanding is that "1471537219" is the ID for the rule action causing the error.  Unfortunately, when I download Configuration Rules, the output does NOT include action IDs, only rule IDs.  For example, knowing which rule caused the error, I can find the rule (<id>1471537217</id>) ID in the output but there is no reference to "1471537219".

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!