SYSTEM AND METHOD FOR DEFINITION, CREATION, MANAGEMENT, TRANSMISSION, AND MONITORING OF ERRORS IN SOA ENVIRONMENT

• US 20130290794A1
• Filed: 03/25/2013
• Published: 10/31/2013
• Est. Priority Date: 04/23/2010
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Murphy, Ronald Francis, Malladi, Sastry K., Deng, Weian, Kumar, Abhinav, Avalani, Bhaven, Mony, Arun Raj
• Granted Patent: US 9,069,665 B2
• Time in Patent Office: Days
• US Class Current: 714/57
• 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 a unique identifier (ID) for each new error data instance;

allowing customization of error data structure through extensions;

managing error instances that conform to the common standard error data structure 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.