System and method for definition, creation, management, transmission, and monitoring of errors in SOA environment

• US 8,407,520 B2
• Filed: 04/23/2010
• Issued: 03/26/2013
• Est. Priority Date: 04/23/2010
• Status: Expired due to Fees

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Murphy, Ronald Francis, Malladi, Sastry K., Deng, Weian, Kumar, Abhinav, Avalani, Bhaven, Mony, Arun Rai
• Primary Examiner(s): TRUONG, LOAN
• Application Number:
  US12/766,712
• Publication Number:
  US 20110264964A1
• Time in Patent Office: 1,068 Days
• Field of Search: 714/48, 714/57, 714/26
• US Class Current: 714/26
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 11/0769 Readable error formats, e.g. cross-platform generic formats, human understandable formats
• CPC Class Codes: G06F 11/0772 Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/55 Testing of service level quality, e.g. simulating service usage

Abstract

A computer-implemented system and method for the definition, creation, management, transmission, and monitoring of errors in a SOA environment. An example embodiment includes: defining a common standard error data structure; automatically generating a unique identifier (ID) for each new error data instance; allowing customization of error data structure through extensions; creation and management of error instances that conform to this structure; ability to group errors across various dimensions; introducing the concept of an error library, the error library including a plurality of localizable error bundles, each of the error bundles including a plurality of error data instances for a particular domain, along with the associated metadata; automatically creating runtime artifacts for each error; ability to transmit errors either as faults or as part of the normal response payload; automatic error metric collection based on various error categories, and finally, tooling to help manage error libraries and reporting errors.

Claims

1. A method comprising:

defining a common standard error data structure;

automatically generating, by use of a data processor, a unique identifier (ID) for each new error data instance;

allowing customization of error data structure through extensions;

managing, by use of the data processor, error instances that conform to the common standard error data structure;

grouping errors across various dimensions;

creating an error library, the error library including a plurality of localizable error bundles, each of the error bundles including a plurality of error data instances for a particular domain, along with the associated metadata;

automatically creating runtime artifacts for each error;

transmitting errors either as faults or as part of a normal response payload;

automatically collecting error metrics based on various error categories; and

providing tooling to help manage error libraries and reporting errors.

2. The method of claim 1 wherein the common standard error data structure includes:

error ID, errorName, organization, category, domain, subdomain, severity, message, resolution, and cause, and exceptionName.

15. The method of claim 1 including providing a plugin to support auto-generation of error management code based on the error library.

3. An apparatus comprising:

a processor; and

an error library tooling to;

define a common standard error data structure;

automatically generate a unique identifier (ID) for each new error data instance;

allow customization of error data structure through extensions;

create and manage error instances that conform to the common standard error data structure;

provide an ability to group errors across various dimensions;

create an error library, the error library including a plurality of localizable error bundles, each of the error bundles including a plurality of error data instances for a particular domain, along with the associated metadata;

automatically create runtime artifacts for each error;

transmit errors either as faults or as part of the normal response payload;

automatically collect error metrics based on various error categories; and

provide tooling to help manage error libraries and reporting errors.

4. The apparatus of claim 3 wherein the common standard error data structure includes:

error ID, errorName, organization, category, domain, subdomain, severity, message, resolution, and cause, and exceptionName.

16. The apparatus of claim 3 being further configured to provide a plugin to support auto-generation of error management code based on the error library.

5. An article of manufacture comprising a non-transitory machine-readable storage medium having machine executable instructions embedded thereon, which when executed by a machine, causes the machine to:

define a common standard error data structure;

automatically generate a unique identifier (ID) for each new error data instance;

allow customization of error data structure through extensions;

create and manage error instances that conform to the common standard error data structure;

provide an ability to group errors across various dimensions;

create an error library, the error library including a plurality of localizable error bundles, each of the error bundles including a plurality of error data instances for a particular domain, along with the associated metadata;

automatically create runtime artifacts tor each error;

transmit errors either as faults or as part of the normal response payload;

automatically collect error metrics based on various error categories; and

provide tooling to help manage error libraries and reporting errors.

6. The article of manufacture as claimed in claim 5 wherein the common standard error data structure includes:

error ID, errorName, organization, category, domain, subdomain, severity, message, resolution, and cause, and exceptionName.

17. The article of manufacture as claimed in claim 5 being further configured to provide a plugin to support auto-generation of error management code based on the error library.

7. A method comprising:

receiving an error type definition specifying a common error structure;

creating, by use of a data processor, an error library, the error library including a plurality of error bundles, each of the error bundles including a plurality of error data instances, the error data instances conforming to the common error structure;

receiving a request to add a new error data instance to the error library;

automatically generating a unique identifier (ID) for the new error data instance, the new error data instance ID being unique among all error data instances in the error library; and

building the error library to create code which registers all error data instances in the error library.

8. The method of claim 7 wherein the error type definition includes parameter definitions from the group:

error ID, error name, organization, category, domain, sub-domain, severity, message, and resolution.

9. The method of claim 7 wherein the error type definition is a customized error type definition that extends the data attributes of a base error type definition.

10. The method of claim 7 including providing a plugin to support auto-generation of error management code based on the error library.

11. An apparatus comprising:

a processor; and

an error library manager to use the processor to;

receive an error type definition specifying a common error structure;

create, by the processor, an error library, the error library including a plurality of error bundles, each of the error bundles including a plurality of error data instances, the error data instances conforming to the common error structure;

receive a request to add a new error data instance to the error library;

automatically generate a unique identifier (ID) for the new error data instance, the new error data instance ID being unique among all error data instances in the error library; and

build the error library to create code which registers all error data instances in the error library.

12. The apparatus of claim 11 wherein the error type definition includes parameter definitions from the group:

error ID, error name, organization, category, domain, sub-domain, severity, message, and resolution.

13. The apparatus of claim 11 wherein the error type definition is a customized error type definition that extends the data attributes of a base error type definition.

14. The apparatus of claim 11 being further configured to provide a plugin to support auto-generation of error management code based on the error library.