Message level processing method in service system structure

Abstract

A message layer exception handling method in a service-oriented architecture. The method uses the exception definition hyperspace and meta-level definition to identify, analyze and process in time the exceptions that occur in the system, especially in the case of multi-level service calls, and provide multi-level Accurate local and remote exception causes, filtered stack information and address information. The method's exception definition hyperspace allocation, segmentation processing, and exception meta-level definition simplify the definition and processing of newly added exceptions due to the continuously expanding system scale; the message layer exception handling method is divided into exception construction and packaging, and trace stack Filtering, exception message encoding and decoding process.

Description

technical field [0001] The invention relates to the technical field of data processing, identification and analysis processing, in particular to an exception processing method in a service-oriented architecture. Background technique [0002] Software systems are becoming more complex in several ways and must deal with a large number of newly added and more difficult exceptions. Traditionally, exception-handling models for programming languages ​​have relied on either language-specific methods of detecting errors and finding error handlers, or relying on the exception-handling mechanisms provided by the operating system. For service-oriented architecture (Service-Oriented Architecture, SOA), many system implementations and specifications define dedicated error or fault handling methods for application development, such as post-event log query, service description language (WSDL) <wsdl:fault>, Simple Object Access Protocol (SOAP) <soap:fault>mechanism. [0003]...

AI Technical Summary

Problems solved by technology

[0004] The common problems in the existing exception handling mechanism are: the exception handling of programming languages ​​(including hierarchical, dedicated exception handling models that support multiple programming languages, such as the . and ) and a set of methods using these mechanisms often lead to loss of useful exception information or new errors due to imperfect exception handling; specification, analysis, verification, and testing methods that attempt to solve system and program exceptions cannot provide accurate information in a timely manner Remote exception information; the incompatibility of exception identification and analysis processing features with the adopted programming language features and methods may cause new errors

From the perspective of software system design, exception or fault handling such as logs, programming languages, service description languages, and Simple Object Access Protocol does not meet the needs of multi-level exception handling in service-oriented architecture, and related development tools are not timely. , Accurately handle exceptions that may occur within the service architecture (such as execution environment, communication protocol, message exchange, extension model, dynamic binding), especially the definition, identification and analysis of exceptions

Images