CN101247419A - Service intermediate layer fault-tolerance method based on XESB - Google Patents
Service intermediate layer fault-tolerance method based on XESB Download PDFInfo
- Publication number
- CN101247419A CN101247419A CN 200810102768 CN200810102768A CN101247419A CN 101247419 A CN101247419 A CN 101247419A CN 200810102768 CN200810102768 CN 200810102768 CN 200810102768 A CN200810102768 A CN 200810102768A CN 101247419 A CN101247419 A CN 101247419A
- Authority
- CN
- China
- Prior art keywords
- service
- fault
- error
- mistake
- tolerant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The present invention provides a service agency layer fault-tolerant method based on XESB. The agency layer adopts politic service fault-tolerant modus to recovery the wrong when service transfer is failure. XESB agency layer is divided into three part error detection, error recovery and fault-tolerant policy by adopting politic service fault-tolerant mechanism. Error detector testing system wrong, error recovery module executing recovery when having wrong, fault-tolerant policy defining detection mode of wrong and correspond relationship between wrong processors. retry mechanism, equivalence service transfer mechanism and multiple service transfer mechanism are provided for executing recovery processing to wrong when service transfer generates wrong. The present invention ensure reliability of service, improving error detection, reuse of fault tolerant component and flexibility of error handling modus.
Description
Technical field
The present invention relates to a kind of service intermediary layer fault-tolerance approach based on XESB, be mainly used in the service of XESB fault-tolerant in.
Background technology
Enhancing along with the Internet advantage, more and more enterprises provides the service based on the Internet, new business model is developed, strengthening gradually alternately between the enterprise operation system, communication and integration problem between the system show especially out, even also have integration problem between the heterogeneous system in enterprises.Original developing instrument and platform can not satisfy the demand that makes up distributed system, in order to reuse existed system, reduce the IT system investment, various distributed component technology have been developed, as the CORBA technology of OMG tissue, the RMI technology in Java camp, the DCOM technology of Microsoft.These technology can solve the communication and the integration problem of distributed system to a certain extent, but exist some problems, bind with tightly coupled communication mode, based on the binary signaling agreement as mutual both sides, and adopt and stride the closely integrated of logical layer, cause scalability issues easily.RMI and DCOM technology are limited to particular platform in addition, can not realize integrated between the heterogeneous system, and the CORBA complicated technology realization drops into high.In order to solve close coupling problem integrated between the distributed system, produced message-oriented middleware technology (MOM).That but most of MOM implementations provide all is the local API that communicates by letter with own nucleus equipment, influenced the transplantability of application program between this type of implementation, thereby cause and to realize being locked in particular server supplier's problem, Tong Xin message is the form of communicating pair agreement in addition, and formulating communication protocol itself is exactly the process of a complexity.
Service-oriented architectural framework (SOA) has proposed a kind of new Design Mode based on the structure operation system of serving.SOA is defined as a kind of application architecture, in this architecture, all functions all are defined as independently service, these services have well-defined callable interface, can be with the sequence call that defines these serve and form operation flow, when service realized changing, service procedure can constant or only need be made little change.Be considered to the implementation that realizes that SOA is best based on the Web service technology of XML, it adopts open standard, as XML, SOAP, WSDL and UDDI, solved the communication between the heterogeneous system, service describing and definition and service are issued and are pinpointed the problems, Web service has strong autonomy, loose coupling, open and can be integrated etc. characteristic, make Web service be applicable to that application program is integrated, B2B is integrated, code and data reusing, and carry out the occasions for communication of client and server by Web, as ecommerce, E-Government, enterprise's application integration, stride the business integration on enterprise border etc.
The key foundation framework that supports SOA is ESB (ESB).ESB is the product that technology such as traditional middleware technology and XML, Web service mutually combine, be used to realize enterprise use different messages accurately, efficient and safe transfer.The appearance of ESB has changed traditional software architecture, the solution more easier than traditional middleware product can be provided, simultaneously it can also eliminate the technological disparity between the isomery application system, allows the different application services can interoperability, realizes communication and integration between the different services.Serve as service intermediary ESB can the service between transformation service logic and data format, service integrated and service business logic are separated, thereby make different application programs can use same service simultaneously, when application program or data change, need not the service of changing and realize.Present various ESB product is mainly paid close attention to integrated and conversion and message route and intermediary's processing of multiple transport protocols, and the support pattern fault-tolerant for service is single, can not satisfy complicated, flexible and changeable application demand.XESB is a kind of implementation of ESB, and it adopts the framework of layering, is divided into transport layer, message layer, service layer and intermediary layer.XESB is based on open standard agreement, mutual based on standard agreement is provided between service consumer and the ISP, and can between different agreements, change, make and adopt the system of differing transmission protocols to intercom mutually, and can carry out intermediary operations such as log record, interface conversion.In workflow technology based on Web service, intermediary's flow process is made up of a plurality of Web services, wherein each service call failure all may cause the failure of whole flow process, therefore, the XESB that transmits infrastructure as service message is necessary for service call provides reliable structure base communication and multiple fault-tolerant processing mode, can be so that client's transparent way is recovered when service call is failed.
Existing product is many reliably calling that message layer supports that reliable transport protocol supports to serve, but it is not enough to serving wrong processing support in service layer, mistake occurring in the request processing procedure just returns to error message the user or can carry out simple retry operation, can not carry out flexible configuration to the detection mode and the wrong reset mode of mistake, enable under complexity, insecure network environment, to ensure reliably calling of service.
Summary of the invention
In order to solve ESB service fault-tolerant processing problem in the prior art, main purpose of the present invention provides a kind of service fault tolerant mechanism based on the XESB system, ensures reliably calling of service.
For achieving the above object, the present invention is by the following technical solutions: a kind of service intermediary layer fault-tolerance approach based on the XESB system, described intermediary layer adopts the service fault-tolerant way based on strategy that mistake is recovered when service call is failed, and described intermediary layer is divided into error detection, mistake recovery, fault-tolerant strategy and error handler; Error detection detects the mistake that takes place in the life cycle of whole intermediary handling process, preserves wrong contextual information when mistake takes place, and comprises the type and the related data of mistake, gives the wrong resume module of recovering; Mistake is recovered the error message by the error detection module submission, and the fault-tolerant strategy of inquiry fault-tolerant strategy thesaurus correspondence calls the corresponding error processor according to fault-tolerant strategy and carries out the mistake recovery; Fault-tolerant strategy has defined wrong detection mode and the corresponding relation between the error handler, and the detection and the reset mode of serving is configured, and error detection and fault processing separate configuration strengthen the flexibility of tolerant system; Fault processing is defined in when making a mistake and how handles.
The present invention compares with other service fault-tolerance approach, has the following advantages:
(1) the present invention is based on the XESB ESB, the service of give information layer and intermediary layer is fault-tolerant.In the reliable delivery of message layer by integrated reliable news guarantee message, guarantee correctly calling of service at intermediary layer by number of mechanisms, ensured reliability of service.
(2) intermediary layer of the present invention service is fault-tolerant based on strategy, can distinguish configuration error and detect and the fault processing mode, has improved the flexibility with fault-tolerant processing of reusing of assembly.
(3) in addition, the invention provides by retry, equivalent service call and many service calls etc. based on correctly the calling of the service fault tolerant mechanism guarantee service of strategy, improved reliability of service.
Description of drawings
Fig. 1 is intermediary layer service fault tolerance module diagram of the present invention;
Fig. 2 serves fault-tolerant flow chart for intermediary layer of the present invention;
Fig. 3 is a retry mechanism schematic diagram in the intermediary layer of the present invention;
Fig. 4 is a service call schematic diagram of mechanism of equal value in the intermediary layer of the present invention;
Fig. 5 is many service calls schematic diagram of mechanism in the intermediary layer of the present invention.
Embodiment
As shown in Figure 1, intermediary layer of the present invention takes retry when service call is failed, call modes such as equivalent service recovers mistake, and can the configuration service fault-tolerant strategy.Serve the fault-tolerant fault-tolerant strategy that is divided into, error detection, mistake are recovered and error handler.
Described fault-tolerant strategy has defined the mode of service error detection and fault processing.Fault-tolerant strategy has defined misclassification, has disposed the corresponding relation between error detection and the fault processing, and each error detector all can be specified a wrong numbering when triggering mistake, and each error handler has also disposed the mistake numbering of handling.After error detector triggered mistake, fault-tolerant strategy found the error handler of coupling to handle according to error number.The user can carry out flexible configuration to fault-tolerant strategy according to demand, and system starts fault-tolerant assembly according to policy configurations when carrying out flow process automatically.
How described error detection finds and catches mistake if having defined.Error detector is divided three classes, one class is unusual the catching to message processing procedure, second class is a time-out error, the time-out error detector has been specified maximum latency when initialization, event listener interface when it has realized operation, pick up counting when service request sends incident listening to,, otherwise trigger error handler if in the time of appointment, return then stop timing.The 3rd class class error detection is by the erroneous trigger condition is set, and the content of message is carried out evaluation judge, if reach error condition then trigger fault processing.
The error message that described wrong recovery is at first submitted to according to error detection module, the fault-tolerant strategy of inquiry fault-tolerant strategy thesaurus correspondence finds corresponding error handler, and the processing method of call error processor is carried out mistake and is recovered.
Described error handler is defined in when making a mistake and how handles, and comprises retry error handler, equivalent service call error processor and many service calls error handler.The retry error handler has been specified the number of retries and the retry time interval when initialization, beginning can successfully be returned or reaches maximum reattempt times up to service call during fault processing every the fixed time service of calling, and this moment is wrong recovers failure.Equivalent service call error processor has been realized the fault processing mechanism that equivalent service is called, and calls the equivalent service that has disposed successively, successfully returns or the failure of all service calls up to serving, and at this moment can return error message.Many service calls error handler has realized many service calls mechanism, calls a plurality of services simultaneously, chooses the service result that needs from a plurality of service responses.In system, preserve the example of a plurality of error handler, directly use when needing, need not all reinitialize at every turn.The example of the corresponding retry error handler of error handler 1,2 grade among Fig. 1, equivalent service call error processor and many service calls error handler.
As Fig. 2 institute, the fault-tolerant processing procedure of intermediary layer service of the present invention is:
(1) at first XESB begins to carry out service logic according to flow process configuration startup intermediary flow process.
(2) according to the configuration of fault-tolerant strategy, the detection method that starts error detector detects the message handling process.
(3) if reach the trigger condition of error detector in the process of implementation, error detector is the triggering wrong method of call error recovery then, execution in step (4), otherwise flow process finishes.
(4) mistake recovery module is preserved wrong contextual information, selects the error handler of coupling according to type of error inquiry fault-tolerant strategy.
(5) call error processor processing mistake is recovered mistake, and flow process finishes.
The present invention is divided into machine-processed 3 kinds of retry mechanism, equivalent service call-by mechanism and many service calls to the processing of service call mistake:
When detecting service call failure mistake, call service once more by retry mechanism, as shown in Figure 3.The service of this mode is fault-tolerant can to solve network or the temporary mistake of server, and the retry time interval and number of retries are most important two parameters of this mode.The retry time interval, oversize meeting increased the service consumer stand-by period, and too short possible breakdown also recovers, if the situation of server overload also can increase the weight of the server burden.At first from contextual information, extract service request and call former service, if call success then wrong the recovery finished.If failure then judge whether to reach maximum reattempt times reaches maximum times and then recovers failure, otherwise waits for that retry interval continues the service of calling up to calling success or reaching maximum reattempt times after the time.
The fault tolerant mechanism that equivalent service is called is the replaceable service consistent with calling interface of pre-defined a plurality of function, and as shown in Figure 4, the service that can call other when calling certain serv-fail reaches fault-tolerant purpose.The equivalent service fault tolerant mechanism requires that redundant ISP is arranged, and the interface of service is the same.Can select the equivalent service call according to the qos parameter of service, improve fault-tolerant accuracy, the minimizing failure recovery time.At first extract service request from contextual information, the service of equal value with this service that inquiry has been disposed selected to call with the service of qos parameter coupling, if call success then wrong recovery is finished.Otherwise if the equivalent service that whether satisfies condition in addition of inquiry not then recover failure, otherwise selects suitable equivalent service to call up to calling all malloc failure mallocs of success or all equivalent service, and this moment is wrong recovers failure.
Under the exigent environment to service reliability, the service that avoid may be returned incorrect result's situation, and this just requires and can test to service result.By calling a plurality of equivalent service simultaneously, the result of each service compared select correct result, as shown in Figure 5.This mode requires to exist a plurality of equivalent service, and the expense of calling simultaneously is bigger.At first extract service request from contextual information, inquire about all equivalent service of this service, call all equivalent service simultaneously, according to configuration the result who serves is compared judgement again, the service result of selecting to satisfy condition returns to the user.If the service result that satisfies condition is arranged then wrong the recovery successfully, if all service calls failures or the service response that does not satisfy condition then wrong recovery are failed.
The present invention can also adopt multiple fault processing mode in a fault-tolerant strategy, as can adopt the mechanism of retry when calling equivalent service, also can call a plurality of equivalent service simultaneously and get the service result of returning at first.
Claims (6)
1, a kind of intermediary layer service fault-tolerance approach based on the XESB system, it is characterized in that: described intermediary layer adopts the service fault-tolerant way based on strategy that mistake is recovered when service call is failed, and described intermediary layer fault-tolerance approach is divided into error detection, mistake recovery, fault-tolerant strategy and error handler; Error detection detects the mistake that takes place in the life cycle of whole intermediary handling process, preserves wrong contextual information when mistake takes place, and comprises the type and the related data of mistake, gives the wrong resume module of recovering; Mistake is recovered the error message by the error detection module submission, and the fault-tolerant strategy of inquiry fault-tolerant strategy thesaurus correspondence calls the corresponding error processor according to fault-tolerant strategy and carries out the mistake recovery; Fault-tolerant strategy has defined wrong detection mode and the corresponding relation between the error handler, and the detection and the reset mode of serving is configured, and error detection and fault processing separate configuration strengthen the flexibility of tolerant system; Fault processing is defined in when making a mistake and how handles.
2, a kind of intermediary layer service fault-tolerance approach according to claim 1 based on the XESB system, it is characterized in that: described mistake is divided into two kinds of situations according to the stage that mistake takes place, need to handle respectively: internal error: in intermediary's flow processing process, make a mistake, do not relate to and call external service; Call the service mistake: when calling external service, make a mistake.
3, a kind of intermediary layer service fault-tolerance approach according to claim 1 based on the XESB system, it is characterized in that: described error detection is made of three class error detection, one class is unusual the catching to message processing procedure, second class is a time-out error, time-out error detects has specified maximum latency when initialization, event listener interface when it has realized operation, when listening to service request transmission incident, pick up counting, if in the time of appointment, return then stop timing, otherwise trigger error handler; The 3rd class class error detection is by the erroneous trigger condition is set, and the content of message is carried out evaluation judge, if reach error condition then trigger fault processing.
4, a kind of intermediary layer service fault-tolerance approach according to claim 1 based on the XESB system, it is characterized in that: described mistake is divided into two kinds of situations according to the stage that mistake takes place, need to handle respectively: internal error: in intermediary's flow processing process, make a mistake, do not relate to and call external service; Call the service mistake: when calling external service, make a mistake.
5, a kind of intermediary layer service fault-tolerance approach according to claim 1 based on the XESB system, it is characterized in that: described fault-tolerant strategy has defined misclassification, disposed the corresponding relation between error detection and the fault processing, each error detection all can be specified a wrong numbering when triggering mistake, each error handler has also disposed the mistake numbering of handling, after error detection module triggered mistake, fault-tolerant strategy found the error handler of coupling to handle according to error number.The user can carry out flexible configuration to fault-tolerant strategy according to demand, and system starts fault-tolerant assembly according to policy configurations when carrying out flow process automatically.
6, a kind of intermediary layer service fault-tolerance approach according to claim 1 based on the XESB system, it is characterized in that: described error handler comprises: three types of retry error handler, equivalent service call error processor and many service calls error handler, described retry error handler has been specified the number of retries and the retry time interval when initialization, can recover failure up to serving successfully to return or reach the maximum reattempt times mistake every the fixed time service of calling during the beginning fault processing; Equivalent service call error processor has been realized the fault processing mechanism that equivalent service is called, and calls the equivalent service that has disposed successively, successfully returns or the failure of all service calls up to serving, and at this moment can return error message; Many service calls error handler has realized many service calls mechanism, calls a plurality of services simultaneously, chooses the service result that needs from a plurality of service responses.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101027684A CN101247419B (en) | 2008-03-26 | 2008-03-26 | Service intermediate layer fault-tolerance method based on XESB |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101027684A CN101247419B (en) | 2008-03-26 | 2008-03-26 | Service intermediate layer fault-tolerance method based on XESB |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101247419A true CN101247419A (en) | 2008-08-20 |
| CN101247419B CN101247419B (en) | 2011-12-07 |
Family
ID=39947617
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101027684A Expired - Fee Related CN101247419B (en) | 2008-03-26 | 2008-03-26 | Service intermediate layer fault-tolerance method based on XESB |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101247419B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102208993A (en) * | 2010-03-12 | 2011-10-05 | 微软公司 | Resilient connectivity health management framework |
| CN102831027A (en) * | 2012-08-29 | 2012-12-19 | 上海交通大学 | Agent-based service-software-system-oriented fault-tolerance method |
| CN104734870A (en) * | 2013-12-19 | 2015-06-24 | 南京理工大学 | Software fault spreading method based on cellular automaton |
| CN109739687A (en) * | 2018-12-03 | 2019-05-10 | 国云科技股份有限公司 | A kind of snapshot management system and method based on Elasticsearch |
| CN112579393A (en) * | 2020-12-21 | 2021-03-30 | 广东电网有限责任公司梅州供电局 | Self-checking method and device for Internet of things terminal, terminal and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7318171B2 (en) * | 2003-03-12 | 2008-01-08 | Intel Corporation | Policy-based response to system errors occurring during OS runtime |
-
2008
- 2008-03-26 CN CN2008101027684A patent/CN101247419B/en not_active Expired - Fee Related
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102208993A (en) * | 2010-03-12 | 2011-10-05 | 微软公司 | Resilient connectivity health management framework |
| CN102831027A (en) * | 2012-08-29 | 2012-12-19 | 上海交通大学 | Agent-based service-software-system-oriented fault-tolerance method |
| CN102831027B (en) * | 2012-08-29 | 2015-01-28 | 上海交通大学 | Agent-based service-software-system-oriented fault-tolerance method |
| CN104734870A (en) * | 2013-12-19 | 2015-06-24 | 南京理工大学 | Software fault spreading method based on cellular automaton |
| CN104734870B (en) * | 2013-12-19 | 2019-03-29 | 南京理工大学 | A kind of software fault propagation law discovery method based on cellular automata |
| CN109739687A (en) * | 2018-12-03 | 2019-05-10 | 国云科技股份有限公司 | A kind of snapshot management system and method based on Elasticsearch |
| CN112579393A (en) * | 2020-12-21 | 2021-03-30 | 广东电网有限责任公司梅州供电局 | Self-checking method and device for Internet of things terminal, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101247419B (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Das et al. | ORBWork: A reliable distributed CORBA-based workflow enactment system for METEOR2 | |
| Miller et al. | WebWork: METEOR 2's web-based workflow management system | |
| CN106502769B (en) | Distributed transaction processing method, apparatus and system | |
| Indrasiri et al. | Microservices for the Enterprise | |
| TWI235299B (en) | Method for providing application cluster service with fault-detection and failure-recovery capabilities | |
| US20020161859A1 (en) | Workflow engine and system | |
| CN101247419B (en) | Service intermediate layer fault-tolerance method based on XESB | |
| US6789114B1 (en) | Methods and apparatus for managing middleware service in a distributed system | |
| US20120030689A1 (en) | Business application integration adapters management system | |
| US8135732B2 (en) | System and method for providing network-based services to users with high availability | |
| CN105282128B (en) | A kind of two-way call method and system based on long connection | |
| WO2006091624A2 (en) | System and method for determining information related to user interactions with an application | |
| US8001424B2 (en) | System and method for fault mapping of exceptions across programming models | |
| US8170896B2 (en) | System and method for electronic business transaction reliability | |
| CN106412141A (en) | Processing method and system for domain name template registration | |
| US20060230109A1 (en) | Mediator-based recovery mechanism for multi-agent system | |
| JP2007058506A (en) | Document management server, document management system, and document management program and its recording medium | |
| Fugini et al. | Recovery of faulty web applications through service discovery | |
| Ezenwoye et al. | A Proxy-Based Approach to Enhancing the Autonomic Behavior in Composite Services. | |
| CN115658078A (en) | Database pre-compiling processing method, device, equipment and medium | |
| Ardagna et al. | Faults and recovery actions for self-healing web services | |
| CN110597716B (en) | Multi-service triggered fault detection processing system and method | |
| Kopp et al. | Fault handling in the web service stack | |
| Ermagan et al. | A fault tolerance approach for enterprise applications | |
| CN102831027B (en) | Agent-based service-software-system-oriented fault-tolerance method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111207 Termination date: 20120326 |