Absent Member.. Absent Member..
Absent Member..
176 views

PPM Support Tip:Logging and Exception enhancements

Logging and Exception enhancements

 

Exception reason is not displayed to user

Application exceptions do not bubble up to the end user.

In a lot of such instances, a valid error message is present in the logs, but the exception with the message gets hidden within other exceptions while propagating up the call stack.

 

An HP internal error has occurred. Please contact HP Project and Portfolio Management support if the problem persists. (KNTA-10023)

 

Exception Correlation: GUID=D1B57AA2-5FA2-B714-F096-1A5837FC4E77

Generated Time=2011/01/11-12:45:43.771 PST

Server Node Name: kintana

 

This message has been reworded to the following:

 

An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:

GUID=D1B57AA2-5FA2-B714-F096-1A5837FC4E77

 

The PPM administrator can then get more details about this exception from the search exceptions page using the GUID shown. The search exceptions page is a new feature introduced as part of this user story.

This page is accessed from Search|Administrative|Exceptions menu item. The PPM administrator needs to have an administrator license and the “Server Tools: Execute admin tools” access grant to access this page.

A screenshot of this page is shown below:

                       

 As shown in the screenshot above the PPM administrator can enter the GUID in the first field and click the “Go” button to get more details about this exception.

 

The screenshot of the view exception’s page is given below:

 

 

 

It consists of the following details:

  1. User – The full name of the logged in user who encountered this exception. This field is empty for a background service exception.
  2. GUID – The GUID identifier of this exception. Most web exceptions are tagged with a GUID. Background service exceptions usually do not have a GUID.
  3. Name – The name of the exception
  4. URL – The URL of the page that encountered this exception
  5. Reason – The reason of the exception. This can be an error message for background service entries.
  6. Node name – The node name where this exception occurred
  7. Generated Time – The time when this exception occurred
  8. Stack trace – The stack trace of the exception

 

This feature is enabled by the following setting in server.conf com.kintana.core.server.LOG_EXCEPTIONS_TO_DB=true

 

Purging of exceptions (except service exceptions)

Exceptions older than 14 days are automatically purged. This value can be controlled by the following server.conf parameter:

com.kintana.core.server.EXCEPTIONS_RETAIN_PERIOD=14

For every 100th exception created this purge cycle is run. This reduces the processing overhead on the PPM server when a lot of exceptions are being created.

 

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Labels (1)
0 Likes
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.