Browse Prior Art Database

DYNAMIC STACK TRACE DIAGNOSTICS DESIGN PATTERN

IP.com Disclosure Number: IPCOM000049773D
Original Publication Date: 2005-Feb-09
Included in the Prior Art Database: 2005-Feb-09
Document File: 2 page(s) / 28K

Publishing Venue

IBM

Abstract

The basic idea is to create a stack trace based on dynamic configuration, whenever required and create a log out of it. That is when an error condition occurs and if there is a configuration that suggests that stack trace be created then, create a stack trace and write it to the log (file). Users will be able to turn the stack trace on and off dynamically. User can also change the severity level for which the stack-trace be created, dynamically.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 1 of 2

DYNAMIC STACK TRACE DIAGNOSTICS DESIGN PATTERN

1. High Level Architecture

1.1 Overall Architecture

This section describes the high level architecture of the Business Process Diagnostics.

1.2 Description

In the business process execution, there are lots of places where exceptions are handled.

This handling can be in terms of

* Throwing
* Catching
* Logging the exceptions

1.2.1 Throwing Exceptions:

Exceptions are thrown by third party code or even by the business process engine / logic.

This exception throwing is typically done in order to indicate an error condition or signal an occurrence of a particular condition.

Almost all of the time exceptions thrown from inside the code are caught by the caller somewhere up in hierarchy and then handled accordingly.

Third-party exceptions follow their own semantics and so do the exceptions thrown by the business process engine / logic.

1.2.2 Catching Exceptions:

Most third party exceptions are caught by business process engine / logic, and then are either logged or converted into appropriate business process engine / logic exceptions.

Most business process engine / logic exceptions are caught by business process engine / logic code and are either logged or converted to another business process engine / logic exception.

Most business process engine / logic exceptions are associated with a concrete exception base class that inherits from language supported exception class. This class contains the information about the exception...