CN108234349A - The method and apparatus for improving SOA system robustness - Google Patents

Abstract

The present invention provides a method and device for improving the robustness of an SOA system. The method includes: receiving a service request for a service-oriented architecture SOA system, and putting the service request into a message queue; reading the SOA system flag bit, and determine the current state of the SOA system according to the flag bit; when the current state of the SOA system is congested, buffer the service request in the message queue, and request the corresponding service request to the service The client feeds back the first reminder information. The invention realizes buffering the service request of the SOA system when the SOA system is in a congested state, and feeds back reminder information to the client corresponding to the service request, thereby improving the robustness of the SOA system and improving the interactive experience of the client.

Description

Method and device for improving robustness of SOA system

technical field

The invention relates to the technical field of data processing, in particular to a method and a device for improving the robustness of an SOA system.

Background technique

The existing service-oriented architecture (Service-Oriented Architecture, SOA) system must comply with the Simple Object Access Protocol (Simple Object Access Protocol, SOAP) in the process of data serialization between applications. Language (Extensible Markup Language, XML) data interaction protocol.

The business process execution language (Business Process Execution Language, BPEL) process encapsulated in the SOA system takes a lot of time when encapsulating and parsing XML data, which makes the SOA system face some data overload caused by wrong requests. , frequent data interaction during the closing period, etc., the system throughput rate will drop sharply, or even downtime.

However, when the throughput rate of the SOA system drops sharply, or even goes down, the existing SOA system will not give users corresponding feedback, and there is no corresponding protection mechanism, which affects the data interaction between the request and the service, and the user experience. Poor degree.

Contents of the invention

The invention provides a method and device for improving the robustness of the SOA system, so as to buffer the service request of the SOA system when the SOA system is in a congested state, and feed back reminder information to the client corresponding to the service request, thereby improving SOA The robustness of the system improves the interactive experience of the client.

In a first aspect, the present invention provides a method for improving the robustness of an SOA system, including:

Receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue;

Read the flag bit of the SOA system, and determine the current state of the SOA system according to the flag bit;

When the current state of the SOA system is congestion, buffer the service request in the message queue, and feed back first reminder information to the client corresponding to the service request.

Optionally, after determining the current state of the SOA system according to the flag bit, the method further includes:

When the current state of the SOA system is non-congested, it is judged whether there is a service request in the message queue, and if there is, the service request at the head of the message queue is delivered to the SOA system.

Optionally, before receiving the service request for the service-oriented architecture SOA system, it also includes:

Acquiring the current operation composite index of the SOA system, the operation composite index includes any of the following:

The CPU usage rate, memory usage rate, and service request response time of the SOA system at the current moment.

Optionally, after obtaining the current running comprehensive index of the SOA system, it further includes:

When judging whether the current operation comprehensive index of the SOA system is less than or equal to the preset threshold, if so, directly submit the service request to the SOA system for processing;

If not, it is judged whether the message queue is full of service requests;

When the message queue is full of service requests, return the currently received service request, and feed back a second reminder message to the client corresponding to the service request;

When the service request is not filled in the message queue, determine whether the currently received service request is consistent with the service request at the tail end of the message queue, if consistent, the value of the counter is incremented by 1; if inconsistent, Then put the currently received service request into the tail of the message queue.

Optionally, after determining that the currently received service request is consistent with the service request queued at the tail of the message queue, the method further includes:

Obtain the value in the counter;

When the value in the counter is greater than the preset upper limit value, take the service request at the tail of the message queue as an abnormal service request, and feed back a third reminder message to the client corresponding to the abnormal service request; and delete the For all abnormal service requests in the message queue, the value in the counter is cleared;

When the value in the counter is less than or equal to the preset upper limit value, put the currently received service request at the tail of the message queue.

In a second aspect, the present invention provides a device for improving the robustness of an SOA system, including:

A receiving module, configured to receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue;

A determination module, configured to read the flag bit of the SOA system, and determine the current state of the SOA system according to the flag bit;

A processing module, configured to buffer the service request in the message queue when the current state of the SOA system is congestion; and feed back first reminder information to the client corresponding to the service request.

Optionally, the processing module is further configured to, after determining the current state of the SOA system according to the flag bit, when the current state of the SOA system is non-congested, determine whether there If there is a service request, submit the service request at the head of the message queue to the SOA system.

Optionally, also include:

The obtaining module is used to obtain the current operation comprehensive index of the SOA system before receiving the service request for the service-oriented architecture SOA system, and the operation comprehensive index includes any of the following:

The CPU usage rate, memory usage rate, and service request response time of the SOA system at the current moment.

Optionally, the processing module is further configured to determine whether the current running comprehensive index of the SOA system is less than or equal to a preset threshold after obtaining the current running comprehensive index of the SOA system, and if so, to serve The request is directly submitted to the SOA system for processing;

If not, it is judged whether the message queue is full of service requests;

When the message queue is full of service requests, return the currently received service request, and feed back a second reminder message to the client corresponding to the service request;

When the service request is not filled in the message queue, determine whether the currently received service request is consistent with the service request at the tail end of the message queue, if consistent, the value of the counter is incremented by 1; if inconsistent, Then put the currently received service request into the tail of the message queue.

Optionally, the processing module is further configured to acquire the value in the counter after determining that the currently received service request is consistent with the service request queued at the tail of the message queue;

When the value in the counter is greater than the preset upper limit value, take the service request at the tail of the message queue as an abnormal service request, and feed back a third reminder message to the client corresponding to the abnormal service request; and delete the For all abnormal service requests in the message queue, the value in the counter is cleared;

When the value in the counter is less than or equal to the preset upper limit value, put the currently received service request at the tail of the message queue.

In a third aspect, the present invention provides a device for improving the robustness of an SOA system, including:

memory for storing programs;

A processor, configured to execute the program stored in the memory, and when the program is executed, the processor is configured to execute the method in any one of the first aspects.

In a fourth aspect, the present invention provides a computer-readable storage medium, including: instructions, which, when run on a computer, cause the computer to execute any method described in the first aspect.

The method and device for improving the robustness of the SOA system provided by the present invention receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue; read the flag bit of the SOA system, and Determine the current state of the SOA system according to the flag bit; when the current state of the SOA system is congested, buffer the service request in the message queue, and feed back the first message to the client corresponding to the service request reminder message. When the SOA system is in a congested state, the service request of the SOA system is buffered, and the reminder information is fed back to the client corresponding to the service request, thereby improving the robustness of the SOA system and enhancing the interactive experience of the client.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is a schematic diagram of the topology of an SOA system according to an embodiment of the present invention;

FIG. 2 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 1 of the present invention;

FIG. 3 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 2 of the present invention;

FIG. 4 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 3 of the present invention;

FIG. 5 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 4 of the present invention;

FIG. 6 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 1 of the present invention;

FIG. 7 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 2 of the present invention;

FIG. 8 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 1 of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of the present invention and the above drawings are used to distinguish similar objects and not necessarily Describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of practice in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

The technical solution of the present invention will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

Below, some terms in this application are explained, so that those skilled in the art can understand:

1) Service-Oriented Architecture (Service-Oriented Architecture, SOA) is a component model that links different functional units (called services) of an application through well-defined interfaces and contracts between these services. The interface is defined in a neutral way, it should be independent of the hardware platform, operating system and programming language that implements the service. This enables services built in a wide variety of systems to interact in a unified and common way.

2) Extensible Markup Language (XML), a subset of the standard general markup language, is a markup language used to mark electronic documents to make them structural. In electronic computers, tags refer to information symbols that computers can understand. Through such tags, computers can process various information such as articles. It can be used to mark data, define data types, and is a source language that allows users to define their own markup language. It is well suited for World Wide Web transport, providing a unified method for describing and exchanging structured data independent of application or vendor. It is a cross-platform and content-dependent technology in the Internet environment, and it is also an effective tool for processing distributed structural information today.

3) Simple Object Access Protocol (Simple Object Access Protocol, SOAP), a protocol specification for exchanging data, is a lightweight, simple protocol based on XML (a subset of the Standard Universal Markup Language), which It is designed to exchange structured and fixed information on the WEB.

4) The World Wide Web (WEB) refers to the network, which is expressed in three forms, namely hypertext (hypertext), hypermedia (hypermedia), and hypertext transfer protocol (HTTP).

5) Business Process Execution Language (BPEL), which is a programming language written in XML and can be used as a formal specification language for automating business processes.

6) Robustness, also known as Fault Tolerance, is used to describe the ability of the system to automatically recover or ignore the fault and continue to operate when a fault occurs.

The existing enterprise SOA system is to solve the information islands caused by the construction of application systems of different scales after 30 years of information construction. many questions. The previous situation was not that there was no data, but that the information was inconsistent, difficult to integrate and unable to achieve interconnection. Solving the above problems is the purpose of SOA system construction. The tasks and main responsibilities undertaken by SOA are divided into the following four main aspects: (1) Specify access criteria (2) Peripheral system registration (3) Service call flow control (4) Service call concurrency control. When assuming the above responsibilities, if SOA wants to meet the data interaction requirements between various systems, it is a matter of course to deal with the problem of data heterogeneity between systems. When SOA performs data interaction between services, it uses XML-based SOAP for data interaction. The control of service requests and responses and the transformation of data are undertaken by the BPEL control flow encapsulated in the SOA system by SOA developers. The input of the responder and the data of the responder are converted, so as to solve the problem that the data heterogeneity between different systems cannot be interconnected. Fig. 1 is a schematic diagram of the topology structure of the SOA system of an embodiment provided by the present invention. At the hardware level, the existing SOA technology uses a three-layer network architecture, uses hardware load balancing to expose a unified network access IP to the outside, and eight production hosts to the inside. For service distribution.

However, the BPEL process encapsulated in the SOA system takes a lot of time when encapsulating and parsing XML data, which makes the SOA system face some situations such as oversending data due to wrong requests and frequent data interaction during the closing period. , there will be a sudden drop in system throughput, or even downtime. When the throughput rate of the SOA system drops sharply or even goes down, the existing SOA system will not give the user corresponding feedback, and there is no corresponding protection mechanism, which will affect the data interaction between the request and the service, and the user experience. Difference.

The method for improving the robustness of the SOA system provided by the present invention aims to solve the above technical problems in the prior art.

The technical solution of the present invention and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.

Fig. 2 is a flow chart of the method for improving the robustness of the SOA system provided by Embodiment 1 of the present invention. As shown in Fig. 2, the method in this embodiment may include:

S101. Receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue.

In this embodiment, the service request for the service-oriented architecture SOA system is placed in the buffer pool in advance, and the service request is managed through the buffer pool. When the message queue in the buffer pool is not full and the service request is legal , put the service request into the message queue of the buffer pool.

S102. Read the flag bit of the SOA system, and determine the current state of the SOA system according to the flag bit.

In this embodiment, the flag bit of the SOA system is read first, and the current state of the SOA is determined according to the logic value of the flag bit. Optionally, when the value of the flag bit is set to true, it is determined that the current state of the SOA system is a congested state, and when the value of the flag bit is false, it is determined that the current state of the SOA system is a non-congested state. Specifically, the flag bit of the SOA system may be a flag bit of the memory of the SOA system, which is used to identify the occupied state of the memory. When the memory usage exceeds the preset upper limit, the logic value of the memory flag bit is true; otherwise, the logic value of the memory flag bit is false.

S103. When the current state of the SOA system is congestion, buffer the service request in the message queue, and feed back first reminder information to the client corresponding to the service request.

In this embodiment, when the current state of the SOA system is congested, the buffer pool communicated with the SOA system buffers the received service request for the SOA system, and feeds back the first request to the client corresponding to the service request. reminder message. Wherein, the first reminder message is used to remind the client that the current SOA system is busy. Specifically, for example, when the SOA system enters a congested state in the case of frequent requests for large amounts of data, at this time, the buffer pool will also give feedback to the request that refuses to enter the buffer pool, and ask it to submit the request later, so that Improve the interactive experience of the entire SOA system.

In this embodiment, by receiving a service request for a service-oriented architecture SOA system, and putting the service request into a message queue; reading the flag bit of the SOA system, and determining the SOA according to the flag bit The current state of the system: when the current state of the SOA system is congestion, buffer the service request in the message queue, and feed back first reminder information to the client corresponding to the service request. When the SOA system is in a congested state, the service request of the SOA system is buffered, and the reminder information is fed back to the client corresponding to the service request, thereby improving the robustness of the SOA system and enhancing the interactive experience of the client.

Fig. 3 is a flow chart of the method for improving the robustness of the SOA system provided by Embodiment 2 of the present invention. As shown in Fig. 3, the method in this embodiment may include:

S201. Receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue.

S202. Read the flag bit of the SOA system, and determine the current state of the SOA system according to the flag bit.

S203. When the current state of the SOA system is congestion, buffer the service request in the message queue, and feed back first reminder information to the client corresponding to the service request.

In this embodiment, for the specific implementation process of step S201-step S203, refer to the relevant description in the method shown in FIG. 2 , which will not be repeated here.

S204. When the current state of the SOA system is non-congested, judge whether there is a service request in the message queue, if yes, perform step S205, and if not, end.

In this embodiment, when the current state of the SOA system is non-congested, the service requests in the message queue of the buffer pool are obtained.

S205. Submit the service request at the head of the message queue to the SOA system.

The message queue in this embodiment is a two-way queue, one end is set as the head of the column, and the other end is set as the tail of the column. The received service requests are arranged at the tail of the message queue in sequence according to the time they are received, and the buffer pool is arranged according to the service requests in the message queue. Submit the service requests at the head of the column to the SOA system in the order of order.

In this embodiment, the received service requests are buffered through the message queue of the buffer pool, and the service request at the head of the queue is delivered to the SOA system according to the arrangement order of the service requests in the message queue of the buffer pool. Therefore, the buffer processing of the service request of the SOA system is realized, and the SOA system is processed according to the order in which the service request is received, so as to prevent the service request from waiting for processing for too long.

FIG. 4 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 3 of the present invention. As shown in FIG. 4, the method in this embodiment may include:

S301. Obtain the current operation comprehensive index of the SOA system.

In this embodiment, the current running comprehensive index of the SOA system can be evaluated by any parameter among the CPU usage rate of the SOA system at the current moment, the memory usage rate, and the service request response time.

S302. Determine whether the current operation comprehensive index of the SOA system is less than or equal to a preset threshold, if not, execute step S303; if yes, execute step S304.

S303. Determine whether the message queue is full of service requests, if yes, execute step S305; if not, execute step S306.

In this embodiment, firstly, the message queue in the buffer pool is detected to determine whether the message queue is full of service requests. Optionally, the message queue may be a first-in-first-out register (First In First Out, FIFO).

S304, directly submit the service request to the SOA system for processing.

S305. Return the currently received service request, and feed back a second reminder message to the client corresponding to the service request.

In this embodiment, when the message queue in the buffer pool is full of service requests, the buffer pool returns the currently received service request to the corresponding client, and feeds back a second reminder message to the client corresponding to the service request. Wherein, the second reminder message is used to remind the client that the current SOA system is busy, please submit the service request later.

S306. Determine whether the currently received service request is consistent with the service request at the tail of the message queue; if yes, perform step S307; if not, perform step S308.

In this embodiment, when the message queue in the buffer pool is not full of service requests, it is further determined whether the service request currently received by the buffer pool is consistent with the service request at the end of the message queue.

S307. Increase the value of the counter by 1.

In this embodiment, a counter is used to count the number of service requests received that are consistent with the service requests at the tail of the message queue.

S308. Put the currently received service request at the tail of the message queue.

In this embodiment, according to whether the current running comprehensive index of the SOA system is less than or equal to the preset threshold, when the current running comprehensive index is greater than the preset threshold, it is further judged whether the message queue in the buffer pool is full of service requests; if When the message queue is full of service requests, the currently received service request is returned, and a second reminder message is fed back to the client corresponding to the service request. Therefore, to a certain extent, the processing load of the SOA system is reduced. When the SOA is inaccessible when the system is down, the buffer pool can buffer some service requests. When the buffer pool message queue is full of service requests, the buffer pool can also The currently received service request is returned in a timely manner, and the client corresponding to the service request is reminded, thereby improving the interactive experience of the client. In addition, in this embodiment, a counter is also used to count the number of times the received service request is repeated, so as to realize the supervision of the received service request.

FIG. 5 is a flowchart of a method for improving the robustness of an SOA system provided by Embodiment 4 of the present invention. As shown in FIG. 5 , on the basis of the method shown in FIG. 4 , the method in this embodiment may include:

S401. Obtain a value in the counter.

S402. When the value in the counter is greater than the preset upper limit, take the service request at the end of the message queue as an abnormal service request, and feed back a third reminder message to the client corresponding to the abnormal service request; and delete all abnormalities in the message queue Service request, the value in the counter is cleared to zero.

In this embodiment, when the value in the obtained counter is greater than the preset upper limit value, it means that repeated service requests have been received. At this time, the service request at the end of the message queue will be regarded as an abnormal service The corresponding client is requested to feed back the third reminder message. Wherein, the third reminder message is used to remind the client to check the service request. And delete all abnormal service requests in the message queue, and clear the value in the counter.

S403. When the value in the counter is less than or equal to the preset upper limit value, put the currently received service request at the tail of the message queue.

In this embodiment, counters are used to supervise the service requests received by the buffer pool. When the value of the obtained counter is greater than the preset upper limit value, it means that repeated service requests have been received. At this time, the message queue tail The service request is regarded as an abnormal service request, and a third reminder message is fed back to the client corresponding to the abnormal service request. In this way, the abnormal service request is prevented from occupying the resources of the message queue of the buffer pool, the impact of the abnormal service request on the SOA system is reduced, and the reliability of the SOA system is improved.

FIG. 6 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 1 of the present invention. As shown in FIG. 6, the device in this embodiment may include:

The receiving module 10 is configured to receive a service request for a service-oriented architecture SOA system, and put the service request into a message queue;

A determining module 20, configured to read the flag bit of the SOA system, and determine the current state of the SOA system according to the flag bit;

The processing module 30 is configured to buffer the service request in the message queue when the current state of the SOA system is congestion; and feed back first reminder information to the client corresponding to the service request.

Optionally, the processing module 30 is further configured to, after determining the current state of the SOA system according to the flag bit, when the current state of the SOA system is non-congested, determine whether the message queue is There is a service request, and if so, the service request at the head of the message queue is delivered to the SOA system.

Optionally, the processing module 30 is further configured to determine whether the current running comprehensive index of the SOA system is less than or equal to a preset threshold after obtaining the current running comprehensive index of the SOA system, and if so, set The service request is directly submitted to the SOA system for processing;

If not, it is judged whether the message queue is full of service requests;

When the message queue is full of service requests, return the currently received service request, and feed back a second reminder message to the client corresponding to the service request;

When the service request is not filled in the message queue, determine whether the currently received service request is consistent with the service request at the tail end of the message queue, if consistent, the value of the counter is incremented by 1; if inconsistent, Then put the currently received service request into the tail of the message queue.

Optionally, the processing module 30 is further configured to acquire the value in the counter after determining that the currently received service request is consistent with the service request queued at the tail of the message queue;

When the value in the counter is greater than the preset upper limit value, take the service request at the tail of the message queue as an abnormal service request, and feed back a third reminder message to the client corresponding to the abnormal service request; and delete the For all abnormal service requests in the message queue, the value in the counter is cleared;

When the value in the counter is less than or equal to the preset upper limit value, put the currently received service request at the tail of the message queue.

This embodiment can execute the technical solutions in the methods shown in FIGS. 2-5 above, and its implementation process and technical effects are similar to those of the above methods, and will not be repeated here.

FIG. 7 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 2 of the present invention. As shown in FIG. 7 , on the basis of the device shown in FIG. 6 , the device in this embodiment may further include:

The obtaining module 40 is used to obtain the current operation comprehensive index of the SOA system before receiving the service request for the service-oriented architecture SOA system, and the operation comprehensive index includes any of the following:

The CPU usage rate, memory usage rate, and service request response time of the SOA system at the current moment.

This embodiment can execute the technical solutions in the methods shown in FIGS. 2-5 above, and its implementation process and technical effects are similar to those of the above methods, and will not be repeated here.

FIG. 8 is a schematic structural diagram of a device for improving the robustness of an SOA system provided by Embodiment 1 of the present invention. As shown in FIG. 8, the device in this embodiment may include:

memory 50 for storing programs;

The processor 60 is configured to execute the program stored in the memory 50. When the program is executed, the processor 60 is configured to execute the technical solutions in the methods shown in FIGS. 2-5.

This embodiment can execute the technical solutions in the methods shown in FIGS. 2-5 above, and its implementation process and technical effects are similar to those of the above methods, and will not be repeated here.

In addition, an embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When at least one processor of the user equipment executes the computer-executable instructions, the user equipment executes the above-mentioned various possibilities. Methods.

Among other things, computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium can be located in the ASIC. Additionally, the ASIC may be located in the user equipment. Of course, the processor and the storage medium can also exist in the communication device as discrete components.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (10)

1. A kind of 1. method for improving SOA system robustness, which is characterized in that including：

   The service request for Enterprise SOA SOA systems is received, and the service request is put into message queue；

   The flag bit of the SOA systems is read, and the current state of the SOA systems is determined according to the flag bit；

   When the current state of the SOA systems is congestion, the service request in the message queue is buffered, and to the service Ask corresponding the first prompting message of client feedback.
2. 2. according to the method described in claim 1, it is characterized in that, described determine the SOA systems according to the flag bit Current state after, further include：

   When the current state of the SOA systems is non-congested, judge with the presence or absence of service request in the message queue, if depositing The service request of the message queue head is then being submitted to the SOA systems.
3. 3. according to the method described in claim 1, it is characterized in that, receiving the clothes for Enterprise SOA SOA systems Before business request, further include：

   The current operation composite index of the SOA systems is obtained, the operation composite index includes following any：

   The central processor CPU utilization rate at SOA system current times, memory usage, service request response time.
4. 4. according to the method described in claim 3, it is characterized in that, in the current operation composite index for obtaining the SOA systems Later, it further includes：

   When judging whether the current operation composite index of the SOA systems is less than or equal to preset threshold value, if so, will clothes Business request is directly submitted to the SOA systems and is handled；

   If it is not, then judge whether be booked service request in the message queue；

   When being booked service request in the message queue, the service request being currently received is returned to, and to the service request Corresponding the second reminder message of client feedback；

   When not being booked service request in the message queue, determine the service request being currently received whether with coming described disappear The service request for ceasing the tail portion of queue is consistent, if unanimously, the value of counter is enabled to increase 1 certainly；If inconsistent, will be currently received Service request be put into the tail portion of the message queue.
5. 5. it according to the method described in claim 4, it is characterized in that, in the service request for determining to be currently received and comes described After the service request of the tail portion of message queue is consistent, further include：

   Obtain the numerical value in the counter；

   When numerical value in the counter is more than preset upper limit value, using the service request of the message queue tail portion as different Normal service request asks corresponding client feedback third reminder message to the exception service；And delete the message queue In the request of all exception services, the value in counter resets；

   When numerical value in the counter is less than or equal to preset upper limit value, the service request being currently received is put into The tail portion of the message queue.
6. 6. a kind of device for improving SOA system robustness, which is characterized in that including：

   Receiving module for receiving the service request for Enterprise SOA SOA systems, and the service request is put into In message queue；

   Determining module for reading the flag bit of the SOA systems, and determines the SOA systems according to the flag bit Current state；

   Processing module, for when the current state of the SOA systems is congestion, the service buffered in the message queue please It asks；And to corresponding the first prompting message of client feedback of the service request.
7. 7. device according to claim 6, which is characterized in that

   The processing module is additionally operable to after the current state that the SOA systems are determined according to the flag bit, described When the current state of SOA systems is non-congested, judge with the presence or absence of service request in the message queue, if in the presence of by institute The service request for stating message queue head is submitted to the SOA systems.
8. 8. device according to claim 6, which is characterized in that further include：

   Acquisition module, for before the service request for Enterprise SOA SOA systems is received, obtaining the SOA systems The current operation composite index of system, the operation composite index include following any：

   The central processor CPU utilization rate at SOA system current times, memory usage, service request response time.
9. 9. device according to claim 8, which is characterized in that

   The processing module is additionally operable to after the current operation composite index of the SOA systems is obtained, judges the SOA systems When whether the current operation composite index of system is less than or equal to preset threshold value, if so, service request is directly submitted to The SOA systems are handled；

   If it is not, then judge whether be booked service request in the message queue；

   When being booked service request in the message queue, the service request being currently received is returned to, and to the service request Corresponding the second reminder message of client feedback；

   When not being booked service request in the message queue, determine the service request being currently received whether with coming described disappear The service request for ceasing the tail portion of queue is consistent, if unanimously, the value of counter is enabled to increase 1 certainly；If inconsistent, will be currently received Service request be put into the tail portion of the message queue.
10. 10. device according to claim 9, which is characterized in that

    The processing module is additionally operable to the clothes in the service request for determining to be currently received and the tail portion for coming the message queue After business request is consistent, the numerical value in the counter is obtained；

    When numerical value in the counter is more than preset upper limit value, using the service request of the message queue tail portion as different Normal service request asks corresponding client feedback third reminder message to the exception service；And delete the message queue In the request of all exception services, the value in counter resets；

    When numerical value in the counter is less than or equal to preset upper limit value, the service request being currently received is put into The tail portion of the message queue.