Debug view

The Debug view displays the stack frame for the suspended threads for each target you are debugging. You can get a stack trace of the execution history.

From the Debug view, you can manage the debugging of a rule project or any Java™ program in the workbench. It displays the stack frame for the suspended threads for each target you are debugging. Each thread is shown as a node in the tree.

The Debug view does not provide a history of all the events occurring in the rule engine. However, a stack trace is a useful debugging tool, particularly when an exception has been thrown in the code or when a method is called from a variety of places within your code and you want to learn from where it is called when a particular problem occurs.

You can get stack trace information of the execution history. The stack lists the classes, and the methods within those classes, that are called at the point where the exception occurs through programmatic access. For example, you can use the StackTraceElement class and the getStackTrace method of the Throwable class.

You can also generate a partial Java stack trace by using the static Thread.dumpStack method or the printStackTrace method of the Throwable class.

If the JVM experiences an internal error, it calls its own signal handler to print out the threads and monitors information.