CN117195129A - Exception handling method based on sandbox system and related equipment - Google Patents
Exception handling method based on sandbox system and related equipment Download PDFInfo
- Publication number
- CN117195129A CN117195129A CN202311169857.1A CN202311169857A CN117195129A CN 117195129 A CN117195129 A CN 117195129A CN 202311169857 A CN202311169857 A CN 202311169857A CN 117195129 A CN117195129 A CN 117195129A
- Authority
- CN
- China
- Prior art keywords
- exception
- exception handling
- abnormal
- result
- type
- 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.)
- Pending
Links
- 244000035744 Hura crepitans Species 0.000 title claims abstract description 76
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000002159 abnormal effect Effects 0.000 claims description 179
- 238000012545 processing Methods 0.000 claims description 96
- 230000005856 abnormality Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 7
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000004927 fusion Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000010355 oscillation Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application discloses an exception handling method and related equipment based on a sandbox system, wherein an operation exception result of a financial business error scene is obtained in the sandbox system, an exception type of the operation exception result is obtained, and meanwhile, an exception handling strategy is directly obtained by combining the exception type with a preset exception handling rule in the sandbox system, the sandbox system finishes exception handling of the operation exception result by utilizing the exception handling strategy, the operation exception result is not required to be reported to a server, and the exception handling strategy can be obtained only by the preset exception classification rule and the preset exception handling rule in the sandbox system, so that the sandbox system can correctly handle the operation exception result.
Description
[ field of technology ]
The application relates to the field of financial service debugging, in particular to an exception handling method based on a sandbox system and related equipment.
[ background Art ]
The financial business system error handling and fault tolerance mechanism is an important solution technology in the field of information technology, and the sandbox system of the open bank is an environment for simulating the joint debugging open application program and provides a series of APIs and functions for developers to integrate and test. The error handling mechanism of the sandboxed system is very important for the stability and reliability of the sandboxed system.
At present, error processing of the sandbox is to report an operation abnormal result to a server in an asynchronous communication mode, and the server issues an abnormal processing strategy corresponding to the operation abnormal result to the sandbox system so as to complete processing of the operation abnormal result. The asynchronous communication mode has the problems of message loss, message repetition and the like, so that the sandboxed system cannot correctly process abnormal operation results.
[ application ]
In view of the above, the present application provides an exception handling method and related equipment based on a sandbox system, so that the sandbox system can correctly handle abnormal operation results.
The specific technical scheme of the first embodiment of the application is as follows: an exception handling method based on a sandbox system, the method comprising: simulating operation of a preset financial business error scene in a sandbox system, and acquiring an operation abnormal result of the financial business error scene; the abnormal operation results are 1 or more; classifying the operation abnormal result by using a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error; obtaining an exception handling strategy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type; performing exception processing on the exception type by using the exception processing strategy to obtain an exception processing result of the exception type; and when the exception handling result is not passing, returning to the step of performing exception handling on the exception type by utilizing the exception handling strategy until the exception handling result is passing, and finishing exception handling of the operation exception result.
Preferably, after the exception handling of the exception type by using the exception handling policy, the method further includes: acquiring a first exception handling frequency of the exception handling strategy for exception handling of the exception type; and stopping the exception handling of the exception type when the first exception handling times exceeds the preset times, and reporting the exception type to a preset server.
Preferably, the method further comprises: when the abnormal processing result is that the abnormal processing result does not pass, performing abnormal processing on the abnormal type according to a preset retry interval time and the abnormal processing strategy; and the retry interval time is the interval of performing exception handling on the exception type by using the exception handling strategy next time.
Preferably, the exception handling policy of the exception type comprises an exception handling policy sequence; the exception handling policy sequence comprises a plurality of exception handling sub-policies which are ordered according to a preset priority ordering rule; the number of the abnormality processing sub-strategies in the abnormality processing strategy sequence of the abnormality type is not less than the preset times; the performing exception handling on the exception type by using the exception handling policy comprises: taking the ith exception handling sub-strategy in the exception handling strategy sequence as a target exception handling strategy, wherein the initial value of i is 1; performing exception handling on the exception type by utilizing the target exception handling strategy; before the step of returning to the step of performing exception handling on the exception type by using the exception handling policy, let i=i+1.
Preferably, the method further comprises: the financial business error scene comprises a plurality of sub business error scenes, a first identifier is set at the beginning of each sub business error scene, and a second identifier is set at the end of each sub business error scene; simulating operation of a preset financial business error scene in the sandbox system to obtain an abnormal operation result of the financial business error scene, wherein the abnormal operation result comprises the following steps: the sandbox system simulates the operation of each sub-service error scene according to the first identifier and the second identifier, and obtains the abnormal sub-service operation result of each sub-service operation scene; all the sub-business operation abnormal results form operation abnormal results of the financial business error scene.
Preferably, the method further comprises: when simulating the operation of a preset financial business error scene in a sandbox system, acquiring the load rate of the sandbox system; acquiring the number of container examples of the sandbox system according to a preset container example setting rule and the load rate; the preset container instance setting rule at least comprises a corresponding relation between the load rate and the number of container instances; configuring container instances of the sandboxed system according to the number of container instances; the container instance is used for packaging the financial business error scene to obtain a software package of the financial business error scene; simulating operation of a preset financial business error scene in the sandbox system to obtain an abnormal operation result of the financial business error scene, wherein the abnormal operation result comprises the following steps: and operating the software package in the sandbox system to obtain an abnormal operation result of the financial business error scene.
Preferably, the method further comprises: when the operation abnormal results are multiple, defining the priorities of different operation abnormal results; performing exception processing on the exception type by using the exception processing strategy to obtain an exception processing result of the exception type, wherein the exception processing result comprises: obtaining a target operation abnormal result; the target operation abnormal result is the operation abnormal result with the highest priority among the current different operation abnormal results; performing exception processing on the target exception type by using the exception processing strategy to obtain a target exception processing result of the target exception type; and deleting the target operation abnormal result when the target abnormal processing result is passing, and returning to the step of acquiring the target operation abnormal result until the abnormal processing result of all the operation abnormal results is passing, and finishing the abnormal processing of the different operation abnormal results.
The specific technical scheme of the second embodiment of the application is as follows: an exception handling system based on a sandbox system, the system comprising: the system comprises an operation abnormal result acquisition module, a classification module, an abnormal processing strategy acquisition module, an abnormal processing module and an abnormal processing result acquisition module; the abnormal operation result acquisition module is used for simulating operation of a preset financial business error scene in the sandbox system and acquiring an abnormal operation result of the financial business error scene; the abnormal operation results are 1 or more; the classification module is used for classifying the operation abnormal result by utilizing a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error; the exception handling policy obtaining module is used for obtaining an exception handling policy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type; the exception handling module is used for carrying out exception handling on the exception type by utilizing the exception handling strategy; the exception handling result obtaining module is configured to obtain an exception handling result of the exception type, and return the step of performing exception handling on the exception type by using the exception handling policy when the exception handling result is failed, until the exception handling result is passed, to complete exception handling of the operation exception result.
The specific technical scheme of the third embodiment of the application is as follows: an exception handling device based on a sandbox system, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the method according to any of the first embodiments of the application.
The specific technical scheme of the fourth embodiment of the application is as follows: a computer readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method according to any of the first embodiments of the application.
The implementation of the embodiment of the application has the following beneficial effects:
according to the application, the operation abnormal result of the financial business error scene is obtained by simulating the operation of the preset financial business error scene in the sandbox system; the abnormal operation results are 1 or more; classifying the operation abnormal result by using a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type includes at least one type of authentication error, network error, database error, or file handling error; obtaining an exception handling strategy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type; performing exception handling on the exception type by using an exception handling strategy to obtain an exception handling result of the exception type; and when the exception handling result is not passing, returning to the step of exception handling the exception type by using the exception handling strategy until the exception handling result is passing, and finishing the exception handling of the operation exception result.
The operation exception result of the financial business error scene is obtained in the sandbox system, the exception type of the operation exception result is obtained, meanwhile, the exception handling strategy is directly obtained by combining the exception type with the preset exception handling rule in the sandbox system, the sandbox system finishes exception handling of the operation exception result by utilizing the exception handling strategy, the operation exception result is not required to be reported to a server, and the exception handling strategy can be obtained only by the preset exception classification rule and the preset exception handling rule in the sandbox system, so that the sandbox system can correctly handle the operation exception result.
[ description of the drawings ]
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of steps of a sandboxed system based exception handling method;
FIG. 2 is a flowchart showing the steps of exception handling for exception types according to a predetermined number of times;
FIG. 3 is a flowchart illustrating steps for modeling sub-business error scenarios using identifiers;
FIG. 4 is a flowchart showing steps in setting the number of container instances for a sandboxed system;
FIG. 5 is a flowchart illustrating steps for handling different abnormal operation results according to a predetermined priority;
FIG. 6 is a block diagram of an exception handling system based on a sandbox system;
601, an abnormal operation result acquisition module; 602. a classification module; 603. an exception handling policy acquisition module; 604. an exception handling module; 605. and an exception handling result acquisition module.
[ detailed description ] of the application
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, in a first embodiment of the present application, a step flow chart of an exception handling method based on a sandbox system is provided, wherein an exception handling policy can be obtained only by a preset exception classification rule and a preset exception handling rule in the sandbox system, so that the sandbox system can correctly handle operation exception results, and the method includes:
step 101, simulating operation of a preset financial business error scene in a sandbox system, and obtaining an abnormal operation result of the financial business error scene; the abnormal operation results are 1 or more;
specifically, a preset abnormal capture statement is utilized in a sandbox system to obtain an operation abnormal result of a financial business error scene, wherein the operation abnormal result can be identity verification failure, access refused, network delay, packet loss, null pointer abnormality and the like;
step 102, classifying the operation abnormal result by using a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error;
specifically, all classification rules for running abnormal results are preset in the abnormal classification rules, and the running abnormal results of the financial business error processing scene are classified to obtain different abnormal types;
step 103, obtaining an exception handling strategy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type;
specifically, the exception handling rules include exception handling policies of each exception type, such as an exception handling policy a, an exception handling policy B, etc., and the exception handling policy a of an exception type is obtained according to the exception type of the financial business error handling scenario;
104, performing exception processing on the exception type by using the exception processing strategy to obtain an exception processing result of the exception type;
specifically, performing exception handling on an exception type by using an exception handling policy A to obtain an exception handling result of the exception type, wherein the exception handling result comprises pass and fail; when the exception handling result is passing, completing exception handling of the operation exception result;
and step 105, returning to the step of performing exception processing on the exception type by using the exception processing strategy when the exception processing result is not passed, and finishing exception processing of the operation exception result when the exception processing result is passed.
Specifically, when the exception handling result is failed, retry handling is performed on the exception handling type by using the exception handling policy A, and the exception handling result after retry is obtained, until the exception handling result is passed, the exception handling of the operation exception result is completed.
The operation exception result of the financial business error scene is obtained in the sandbox system, the exception type of the operation exception result is obtained, meanwhile, the exception handling strategy is directly obtained by combining the exception type with the preset exception handling rule in the sandbox system, the sandbox system finishes exception handling of the operation exception result by utilizing the exception handling strategy, the operation exception result is not required to be reported to a server, and the exception handling strategy can be obtained only by the preset exception classification rule and the preset exception handling rule in the sandbox system, so that the sandbox system can correctly handle the operation exception result.
In an embodiment, referring to fig. 2, after performing the exception processing on the exception type by using the exception processing policy, step 105 further includes:
step 201, obtaining a first exception handling frequency of the exception handling policy for exception handling of the exception type;
and 202, stopping exception handling of the exception type when the first exception handling times exceed preset times, and reporting the exception type to a preset server.
Specifically, the number of times of exception handling of the exception type by the exception handling policy a, such as 2 times, is obtained; when the preset times are 3 times, if the abnormal processing result is failed, retrying the abnormal type by using an abnormal processing strategy A; and stopping the exception handling of the exception type and reporting the exception type to the server when the exception handling result is still not passed after 3 times of exception handling are carried out on the exception type by using the exception handling strategy A. If the number of the abnormal processing times exceeds the preset number, if the result is still not passed, the abnormal processing strategy cannot solve the abnormal operation result, and the abnormal operation result needs to be reported to a server for manual problem investigation, so that each abnormal operation result can be ensured to be solved.
In a specific embodiment, the method further comprises: when the abnormal processing result is that the abnormal processing result does not pass, performing abnormal processing on the abnormal type according to a preset retry interval time and the abnormal processing strategy; and the retry interval time is the interval of performing exception handling on the exception type by using the exception handling strategy next time.
Specifically, the preset retry interval time is 3 minutes, and when the exception type is retried by using the exception handling policy a, the interval between the last exception handling and the current retry handling is 3 minutes. By setting the retry time interval, the exception handling strategy processes the exception type for a plurality of times, and the problems of failure of exception handling and the like caused by temporary faults of the sandbox system due to the problems of network oscillation and the like are avoided.
In a specific embodiment, the exception handling policy of the exception type comprises a sequence of exception handling policies; the exception handling policy sequence comprises a plurality of exception handling sub-policies which are ordered according to a preset priority ordering rule; the number of the abnormality processing sub-strategies in the abnormality processing strategy sequence of the abnormality type is not less than the preset times; the performing exception handling on the exception type by using the exception handling policy comprises: taking the ith exception handling sub-strategy in the exception handling strategy sequence as a target exception handling strategy, wherein the initial value of i is 1; performing exception handling on the exception type by utilizing the target exception handling strategy; before the step of returning to the step of performing exception handling on the exception type by using the exception handling policy, let i=i+1.
Specifically, the exception handling policy includes an exception handling policy sequence, where the exception handling policy sequence includes n exception handling sub-policies, which are respectively exception handling sub-policies a, ordered according to a preset priority ordering rule 1 Exception handling sub-policy a 2 … … exception handling sub-policy a n The method comprises the steps of carrying out a first treatment on the surface of the At the first exception handling, an exception handling sub-policy a is utilized 1 Processing the abnormal type; in the second exception handling, the exception handling sub-strategy a is utilized 2 And processing the exception type, and so on until the exception result is passed, completing exception processing. By setting different exception handling sub-strategies, the exception types are subjected to different exception handling sub-strategies for a plurality of times, the probability of success of exception type handling is improved, meanwhile, the exception handling sub-strategies with higher ordering are preferentially used, the success time of exception type handling is shortened, and the exception handling efficiency is improved.
In an embodiment, referring to fig. 3, the method further includes:
step 301, the financial business error scene includes a plurality of sub business error scenes, a first identifier is set at a start bit of each sub business error scene, and a second identifier is set at an end bit of each sub business error scene;
in step 101, simulating operation of a preset financial business error scene in a sandbox system, and obtaining an abnormal operation result of the financial business error scene, including:
step 302, the sandbox system simulates the operation of each sub-service error scene according to the first identifier and the second identifier, and obtains the abnormal sub-service operation result of each sub-service operation scene; all the sub-business operation abnormal results form operation abnormal results of the financial business error scene.
Specifically, the transaction management function using the sandbox system ensures the atomicity of the sub-business operation scenario, including: by adding the first identification bit and the second identification, the sandbox system is ensured to simulate the fusion service error scene in the process of simulating the fusion service error scene, and the simulation of each subtask error scene in the financial service error scene is independent and uncorrelated, so that the corresponding subtask error scene can be quickly found when an operation abnormal result is positioned, the efficiency of error checking is improved, and meanwhile, when the abnormal processing fails, rollback transaction is carried out on the subtask scene by using the first identifier and the second identifier, and the consistency of the subtask operation scene of each version is ensured.
In a specific embodiment, referring to fig. 4, the method further includes:
step 401, obtaining the load rate of a sandbox system when simulating the operation of a preset financial business error scene in the sandbox system;
step 402, obtaining the number of container examples of the sandbox system according to preset container example setting rules and the load rate; the preset container instance setting rule at least comprises a corresponding relation between the load rate and the number of container instances;
step 403, configuring container instances of the sandboxed system according to the number of container instances; the container instance is used for packaging the financial business error scene to obtain a software package of the financial business error scene;
in step 101, simulating operation of a preset financial business error scene in a sandbox system, and obtaining an abnormal operation result of the financial business error scene, including:
and step 404, running the software package in the sandbox system to obtain an abnormal running result of the financial business error scene.
Specifically, when the load of the sandbox system is higher, the number of the container instances is increased according to a preset container instance setting rule, wherein the preset container instance setting rule at least comprises the corresponding relation between the load rate and the number of the container instances, such as the corresponding relation between different CPU (central processing unit) utilization rates, memory use rates, request amounts and the number of the container instances.
In a specific embodiment, referring to fig. 5, the method further includes:
step 501, defining priorities of different operation abnormal results when the operation abnormal results are multiple;
in step 104, performing exception processing on the exception type by using the exception processing policy to obtain an exception processing result of the exception type, including:
step 502, obtaining a target operation abnormal result; the target operation abnormal result is the operation abnormal result with the highest priority among the current different operation abnormal results;
step 503, performing exception processing on the target exception type by using the exception processing strategy to obtain a target exception processing result of the target exception type;
and step 504, deleting the target operation abnormal result when the target abnormal processing result is passing, and returning to the step of obtaining the target operation abnormal result until all the abnormal processing results of the operation abnormal result are passing, and completing the abnormal processing of the different operation abnormal results.
Specifically, when the abnormal operation results are multiple, defining the priorities of different abnormal operation results, for example, the abnormal operation results comprise Q1-Q5, wherein the priority of Q1 is highest, and the priority of Q5 is lowest; when the abnormal operation result is processed, the Q1 is processed preferentially, when the Q1 processing is completed, the Q1 is deleted, the Q2 is processed, and so on until the Q5 is processed, and the abnormal processing is ended. By defining the priority of different operation abnormal results, the operation abnormal results with higher priority are ensured to be processed preferentially; the operation abnormal result with higher priority is usually an important abnormal problem in the sandbox system, and the operation abnormal result with higher priority is preferentially processed, so that the stability of the sandbox system is improved.
In a specific embodiment, referring to fig. 6, a second embodiment of the present application provides an exception handling system based on a sandbox system, the system comprising: an operation exception result acquisition module 601, a classification module 602, an exception handling policy acquisition module 603, an exception handling module 604, and an exception handling result acquisition module 605; the abnormal operation result obtaining module 601 is configured to simulate operation of a preset financial service error scene in a sandbox system, and obtain an abnormal operation result of the financial service error scene; the abnormal operation results are 1 or more; the classification module 602 is configured to classify the operation abnormal result by using a preset abnormal classification rule, so as to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error; the exception handling policy obtaining module 603 is configured to obtain an exception handling policy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type; the exception handling module 604 is configured to perform exception handling on the exception type by using the exception handling policy; the exception handling result obtaining module 605 is configured to obtain an exception handling result of the exception type, and return to the step of performing exception handling on the exception type by using the exception handling policy when the exception handling result is failed, until the exception handling result is passed, and complete exception handling of the running exception result.
By using the system, the operation abnormal result of the financial business error scene can be obtained in the sandbox system, the abnormal type of the operation abnormal result is obtained, meanwhile, the abnormal processing strategy is directly obtained by combining the abnormal type with the preset abnormal processing rule in the sandbox system, the sandbox system finishes the abnormal processing of the operation abnormal result by using the abnormal processing strategy, the operation abnormal result is not required to be reported to a server, and the abnormal processing strategy can be obtained only by the preset abnormal classification rule and the preset abnormal processing rule in the sandbox system, so that the sandbox system can correctly process the operation abnormal result.
In a specific embodiment, a third embodiment of the present application provides an exception handling apparatus based on a sandbox system, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the method according to any of the first embodiments of the present application.
In a specific embodiment, a fourth embodiment of the application provides a computer-readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method according to any one of claims 1 to 7.
Those skilled in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a non-volatile computer readable storage medium, and where the program, when executed, may include processes in the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (10)
1. An exception handling method based on a sandbox system, the method comprising:
simulating operation of a preset financial business error scene in a sandbox system, and acquiring an operation abnormal result of the financial business error scene; the abnormal operation results are 1 or more;
classifying the operation abnormal result by using a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error;
obtaining an exception handling strategy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type;
performing exception processing on the exception type by using the exception processing strategy to obtain an exception processing result of the exception type;
and when the exception handling result is not passing, returning to the step of performing exception handling on the exception type by utilizing the exception handling strategy until the exception handling result is passing, and finishing exception handling of the operation exception result.
2. The exception handling method based on sandboxed system of claim 1, wherein after said exception handling of said exception type using said exception handling policy, further comprising:
acquiring a first exception handling frequency of the exception handling strategy for exception handling of the exception type;
and stopping the exception handling of the exception type when the first exception handling times exceeds the preset times, and reporting the exception type to a preset server.
3. The sandboxed system based exception handling method of claim 1, said method further comprising: when the abnormal processing result is that the abnormal processing result does not pass, performing abnormal processing on the abnormal type according to a preset retry interval time and the abnormal processing strategy; and the retry interval time is the interval of performing exception handling on the exception type by using the exception handling strategy next time.
4. The sandboxed system-based exception handling method of claim 2, wherein: the exception handling policies of the exception type include an exception handling policy sequence; the exception handling policy sequence comprises a plurality of exception handling sub-policies which are ordered according to a preset priority ordering rule; the number of the abnormality processing sub-strategies in the abnormality processing strategy sequence of the abnormality type is not less than the preset times;
the performing exception handling on the exception type by using the exception handling policy comprises:
taking the ith exception handling sub-strategy in the exception handling strategy sequence as a target exception handling strategy, wherein the initial value of i is 1;
performing exception handling on the exception type by utilizing the target exception handling strategy;
before the step of returning to the step of performing exception handling on the exception type by using the exception handling policy, let i=i+1.
5. The sandboxed system based exception handling method of claim 1, said method further comprising: the financial business error scene comprises a plurality of sub business error scenes, a first identifier is set at the beginning of each sub business error scene, and a second identifier is set at the end of each sub business error scene;
simulating operation of a preset financial business error scene in the sandbox system to obtain an abnormal operation result of the financial business error scene, wherein the abnormal operation result comprises the following steps:
the sandbox system simulates the operation of each sub-service error scene according to the first identifier and the second identifier, and obtains the abnormal sub-service operation result of each sub-service operation scene; all the sub-business operation abnormal results form operation abnormal results of the financial business error scene.
6. The sandboxed system based exception handling method of claim 1, said method further comprising: when simulating the operation of a preset financial business error scene in a sandbox system, acquiring the load rate of the sandbox system;
acquiring the number of container examples of the sandbox system according to a preset container example setting rule and the load rate; the preset container instance setting rule at least comprises a corresponding relation between the load rate and the number of container instances;
configuring container instances of the sandboxed system according to the number of container instances; the container instance is used for packaging the financial business error scene to obtain a software package of the financial business error scene;
simulating operation of a preset financial business error scene in the sandbox system to obtain an abnormal operation result of the financial business error scene, wherein the abnormal operation result comprises the following steps:
and operating the software package in the sandbox system to obtain an abnormal operation result of the financial business error scene.
7. The sandboxed system based exception handling method of claim 1, said method further comprising: when the operation abnormal results are multiple, defining the priorities of different operation abnormal results;
performing exception processing on the exception type by using the exception processing strategy to obtain an exception processing result of the exception type, wherein the exception processing result comprises:
obtaining a target operation abnormal result; the target operation abnormal result is the operation abnormal result with the highest priority among the current different operation abnormal results;
performing exception processing on the target exception type by using the exception processing strategy to obtain a target exception processing result of the target exception type;
and deleting the target operation abnormal result when the target abnormal processing result is passing, and returning to the step of acquiring the target operation abnormal result until the abnormal processing result of all the operation abnormal results is passing, and finishing the abnormal processing of the different operation abnormal results.
8. An exception handling system based on a sandbox system, said system comprising: the system comprises an operation abnormal result acquisition module, a classification module, an abnormal processing strategy acquisition module, an abnormal processing module and an abnormal processing result acquisition module;
the abnormal operation result acquisition module is used for simulating operation of a preset financial business error scene in the sandbox system and acquiring an abnormal operation result of the financial business error scene; the abnormal operation results are 1 or more;
the classification module is used for classifying the operation abnormal result by utilizing a preset abnormal classification rule to obtain an abnormal type of the operation abnormal result; the exception type comprises at least one type of authentication error, network error, database error or file processing error;
the exception handling policy obtaining module is used for obtaining an exception handling policy of the exception type according to the exception type and a preset exception handling rule; the preset exception handling rules at least comprise exception handling strategies of each exception type;
the exception handling module is used for carrying out exception handling on the exception type by utilizing the exception handling strategy;
the exception handling result obtaining module is configured to obtain an exception handling result of the exception type, and return the step of performing exception handling on the exception type by using the exception handling policy when the exception handling result is failed, until the exception handling result is passed, to complete exception handling of the operation exception result.
9. An exception handling device based on a sandbox system, comprising a memory and a processor, characterized in that the memory stores a computer program which, when executed by the processor, causes the processor to perform the steps of the method according to any of claims 1 to 7.
10. A computer readable storage medium storing a computer program, which when executed by a processor causes the processor to perform the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311169857.1A CN117195129A (en) | 2023-09-11 | 2023-09-11 | Exception handling method based on sandbox system and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311169857.1A CN117195129A (en) | 2023-09-11 | 2023-09-11 | Exception handling method based on sandbox system and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117195129A true CN117195129A (en) | 2023-12-08 |
Family
ID=88990172
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311169857.1A Pending CN117195129A (en) | 2023-09-11 | 2023-09-11 | Exception handling method based on sandbox system and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117195129A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117914687A (en) * | 2024-03-20 | 2024-04-19 | 深圳市派勤电子技术有限公司 | Management method and system of industrial computer server |
-
2023
- 2023-09-11 CN CN202311169857.1A patent/CN117195129A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117914687A (en) * | 2024-03-20 | 2024-04-19 | 深圳市派勤电子技术有限公司 | Management method and system of industrial computer server |
| CN117914687B (en) * | 2024-03-20 | 2024-05-14 | 深圳市派勤电子技术有限公司 | Management method and system of industrial computer server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN117195129A (en) | Exception handling method based on sandbox system and related equipment | |
| CN111667334B (en) | Audit failure order processing method and device, computer equipment and storage medium | |
| CN111258591B (en) | Program deployment task execution method, device, computer equipment and storage medium | |
| CN111210350A (en) | Block chain transaction method and device, computer equipment and storage medium | |
| CN109325058B (en) | Rule batch comparison method, device, computer equipment and storage medium | |
| CN113163011A (en) | Method, system, device and storage medium for modifying data in block chain | |
| CN110704312A (en) | Pressure testing method and device, computer equipment and storage medium | |
| CN112395202A (en) | Interface automation test method and device, computer equipment and storage medium | |
| CN115048257A (en) | System service function verification method and device, computer equipment and storage medium | |
| CN111966461B (en) | Virtual machine cluster node guarding method, device, equipment and storage medium | |
| CN110647439A (en) | Method and device for confirming block chain system deployment, computer equipment and storage medium | |
| CN111949553B (en) | Rule engine-based scene case testing method and device | |
| CN111131329A (en) | Data consensus method and device for block chain system and hardware equipment | |
| CN112561506A (en) | Live broadcast data processing method, system, device and medium based on virtual currency | |
| CN114527974B (en) | Method and device for realizing business function of software product and computer equipment | |
| CN111737351A (en) | Transaction management method and device for distributed management system | |
| CN114579473B (en) | Application testing method, device, equipment and storage medium | |
| CN111736917B (en) | Data verification method and device, computer equipment and storage medium | |
| CN114564358A (en) | Method, apparatus, device, medium and product for checking compliance of change operations | |
| CN108600312A (en) | A kind of multi-threaded parallel method for down loading based on file block | |
| CN114385498A (en) | Performance test method, system, computer equipment and readable storage medium | |
| CN112860702A (en) | Test execution work order verification method and device, computer equipment and storage medium | |
| CN113360389A (en) | Performance test method, device, equipment and storage medium | |
| CN110740062A (en) | Breakpoint resume method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |