Browse Prior Art Database

Network wide identification of error conditions

IP.com Disclosure Number: IPCOM000010100D
Original Publication Date: 2002-Oct-23
Included in the Prior Art Database: 2002-Oct-23
Document File: 1 page(s) / 35K

Publishing Venue

IBM

Abstract

In a messaging system it is often difficult to match up the error reported on the originator to the errors reported in the traces of other machines. This idea is the labelling of an error with enough information to form a network-wide unique identification. Then when an error is received in response to a network operation, the error trace can be quickly identified in all machines through which the error has passed.

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

Page 1 of 1

Network wide identification of error conditions

In a messaging system, messages typically travel through several intermediates on the way to their destination. Errors happening on the target machine (or any intermediate) are flowed back to the originator. It is often difficult to match up the error reported on the originator to the errors reported in the traces of other machines (ie some devices can trace but not transmit stack traces).

     This idea is the labelling of an error with enough information to form a network-wide unique identification. This information could for example comprise machine id; queue manager id; exception type id; and exception id. Then when an error is received in response to a network operation, the error trace can quickly be identified on all machines through which the error has passed. Unique identification allows these to be identified exactly and unambiguously.

     Identification of errors at each machine can lead to a better understanding of the cause and course of the exception. This may aid diagnosis, or solution development.

Disclosed by International Business Machines Corporation