CN106648944B - Method and device for processing exception - Google Patents
Method and device for processing exception Download PDFInfo
- Publication number
- CN106648944B CN106648944B CN201610850344.0A CN201610850344A CN106648944B CN 106648944 B CN106648944 B CN 106648944B CN 201610850344 A CN201610850344 A CN 201610850344A CN 106648944 B CN106648944 B CN 106648944B
- Authority
- CN
- China
- Prior art keywords
- exception
- code
- abnormal
- rule base
- processing logic
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure discloses a method and a device for processing exception. The method comprises the following steps: the method comprises the steps of obtaining abnormal codes generated by a workflow, reading processing logics corresponding to the abnormal codes from a preset rule base, wherein the rule base comprises the processing logics corresponding to at least two kinds of abnormal codes, and calling the read processing logics to process the abnormity represented by the abnormal codes, so that the abnormity is automatically processed, the abnormity does not need to be manually solved, and the aim of improving the abnormity processing efficiency is fulfilled.
Description
Technical Field
The present disclosure relates to the field of information processing, and in particular, to a method and an apparatus for processing an exception.
Background
Workflow, refers to the automation of a portion or the whole of a business process in a computer application environment. During the execution of the workflow, some unexpected exceptions often occur, such as absence of a transactor, no finding of a next business link, and the like. Once these anomalies occur, the entire business cannot be pushed down.
At present, the workflow usually directly throws the exception into the service system log, and the information operation and maintenance manager manually finds the exception information in the service system log, and manually solves the exception with the support of the system developer. The process of exception resolution is very complicated, the exception handling efficiency is low, and the instability of the system is increased correspondingly.
Disclosure of Invention
In view of the above, the present disclosure provides a method and an apparatus for handling an exception, so as to achieve the purpose of improving exception handling efficiency.
In one aspect of an embodiment of the present disclosure, a method of handling exceptions is provided, the method comprising: acquiring abnormal codes generated by a workflow, reading processing logic corresponding to the abnormal codes from a preset rule base, wherein the rule base comprises the processing logic corresponding to at least two kinds of abnormal codes, and calling the read processing logic to process the abnormality represented by the abnormal codes.
Optionally, the exception code includes an exception source code segment and an exception type code segment, where the exception source code segment is used to store the exception source code, and the exception type code segment is used to store the exception type code. The rule base is at least two rule bases, wherein each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. The processing logic for reading the exception code from the preset rule base includes: and according to the abnormal source code stored in the abnormal source code section of the abnormal code, reading the processing logic corresponding to the abnormal type code from the rule base corresponding to the abnormal source code.
Optionally, the exception code includes an exception level code segment, and the exception level code segment is used for storing an exception level. The calling the read processing logic to process the exception represented by the exception code comprises: and sequencing the abnormal codes according to the abnormal levels stored in the abnormal level code segments of the abnormal codes, and calling the read processing logic to process the abnormal represented by the abnormal codes according to the sequence of the sequenced abnormal codes.
Optionally, the exception code includes an exception source code segment, an exception type code segment, and an exception level code segment, where the exception source code segment is configured to store an exception source code, the exception type code segment is configured to store an exception type code, and the exception level code segment is configured to store an exception level. The rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logics corresponding to different abnormal type codes; each exception source code corresponds to an exception code pool. The processing logic for reading the exception code from the preset rule base includes: and according to the abnormal source code stored in the abnormal source code section of the abnormal code, reading the processing logic corresponding to the abnormal type code from the rule base corresponding to the abnormal source code. The calling the read processing logic to process the exception represented by the exception code comprises: finding out an abnormal code pool corresponding to an abnormal source code of the abnormal code, sending the abnormal code and the read processing logic to the abnormal code pool, sorting the abnormal codes in the abnormal code pool according to the abnormal level stored in the abnormal level code section of the abnormal code, and calling the corresponding processing logic to process the abnormality represented by the abnormal code according to the order of the sorted abnormal codes in the abnormal code pool.
Optionally, the method further comprises: when the rule base does not have the processing logic corresponding to the abnormal code, the abnormal code is sent to an abnormal processing center, the corresponding processing logic fed back by the abnormal processing center aiming at the abnormal code is received, and the processing logic corresponding to the abnormal code is added to the rule base.
In another aspect of embodiments of the present disclosure, there is provided an apparatus for handling an exception, the apparatus including: and the acquisition module is configured to acquire the exception code generated by the workflow. And the logic reading module is configured to read the processing logic corresponding to the abnormal code from a preset rule base, wherein the rule base comprises the processing logic corresponding to at least two kinds of abnormal codes. And the exception handling module is configured to call the read processing logic to handle the exception represented by the exception code.
Optionally, the exception code includes an exception source code segment and an exception type code segment, where the exception source code segment is used to store the exception source code, and the exception type code segment is used to store the exception type code. The rule base is at least two rule bases, wherein each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. The logic read module comprises: and the rule base searching submodule is configured to search out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code segment of the abnormal code. And the logic reading submodule is configured to read processing logic corresponding to the abnormal type code from a rule base corresponding to the abnormal source code according to the abnormal type code stored in the abnormal type code segment of the abnormal code.
Optionally, the exception code includes an exception level code segment, and the exception level code segment is used for storing an exception level. The exception handling module comprises: and the sorting submodule is configured to sort the exception codes according to the exception grades stored in the exception grade code segments of the exception codes. And the processing submodule is configured to call the read processing logic to process the exception represented by the exception code according to the sequence of the sorted exception codes.
Optionally, the exception code includes an exception source code segment, an exception type code segment, and an exception level code segment, where the exception source code segment is configured to store an exception source code, the exception type code segment is configured to store an exception type code, and the exception level code segment is configured to store an exception level; the rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logics corresponding to different abnormal type codes; each exception source code corresponds to an exception code pool. The logic read module comprises: and the rule base searching submodule is configured to search out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code segment of the abnormal code. And the logic reading submodule is configured to read processing logic corresponding to the abnormal type code from a rule base corresponding to the abnormal source code according to the abnormal type code stored in the abnormal type code segment of the abnormal code. The exception handling module comprises: and the code pool searching submodule is configured to search an abnormal code pool corresponding to the abnormal source code of the abnormal code. A sending submodule configured to send the exception code and the read processing logic to the exception code pool. And the sorting submodule is configured to sort the exception codes in the exception code pool according to the exception grades stored in the exception grade code segments of the exception codes. And the processing submodule is configured to call corresponding processing logic to process the exception represented by the exception code according to the sequence of the sequenced exception code in the exception code pool.
Optionally, the apparatus further comprises: and the sending center module is configured to send the exception code to an exception handling center when the processing logic corresponding to the exception code does not exist in the rule base. A feedback receiving module configured to receive corresponding processing logic of the exception processing center for the exception code feedback. And the logic adding module is configured to add the processing logic corresponding to the abnormal code to the rule base.
According to the technical scheme, due to the fact that the abnormal code generated by the workflow is obtained, the processing logic corresponding to the abnormal code is read from the preset rule base, and the read processing logic is called to process the abnormity represented by the abnormal code, the abnormity processing is automatically completed, the abnormity does not need to be manually solved, and the purpose of improving the abnormity processing efficiency is achieved.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure without limiting the disclosure. In the drawings:
FIG. 1 is a schematic diagram of an implementation environment shown in accordance with an exemplary embodiment.
FIG. 2 is a flow chart illustrating a method of handling exceptions according to an exemplary embodiment of the present disclosure.
FIG. 3 is a flowchart illustrating a method of handling exceptions according to another exemplary embodiment of the present disclosure.
FIG. 4 is a flowchart illustrating a method of handling exceptions according to yet another exemplary embodiment of the present disclosure.
FIG. 5 is a flowchart illustrating a method of handling exceptions according to yet another exemplary embodiment of the present disclosure.
FIG. 6 is a block diagram illustrating an apparatus for handling exceptions according to an exemplary embodiment of the present disclosure.
Fig. 7 is a block diagram illustrating an apparatus for handling an exception according to another exemplary embodiment of the present disclosure.
Fig. 8 is a block diagram illustrating an apparatus for handling an exception according to still another exemplary embodiment of the present disclosure.
Fig. 9 is a block diagram illustrating an apparatus for handling an exception according to still another exemplary embodiment of the present disclosure.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
FIG. 1 is a schematic diagram of an implementation environment shown in accordance with an exemplary embodiment. The implementation environment includes: a computer 101. The computer 101 applies the method for processing the exception provided by the embodiment of the present disclosure. The computer 101 may also be used to execute a workflow. During the execution of the workflow by the computer 101, if an exception occurs, the workflow will generate an exception code corresponding to the exception. Furthermore, the method for processing the exception provided by the example of the present disclosure may obtain an exception code generated by the workflow, and process the exception represented by the exception code.
It is to be understood that the implementation environment shown in fig. 1 is only for illustrating the methods provided by the embodiments of the present disclosure, and does not constitute a limitation on the embodiments of the present disclosure.
FIG. 2 is a flow chart illustrating a method of handling exceptions according to an exemplary embodiment of the present disclosure. The method may be applied to a computer 101 as shown in fig. 1. The method can comprise the following steps:
in step 210, exception codes generated by the workflow are obtained.
For example, if the workflow cannot find a transactor, cannot find the next link, etc. during execution, an exception code indicating a corresponding exception may be generated. Wherein, the exception code can be coded in the form of any combination of numbers and/or letters.
In step 220, the processing logic corresponding to the abnormal code is read from a preset rule base, wherein the rule base includes processing logic corresponding to at least two kinds of abnormal codes.
The rule base can be preset locally on a computer to which the method provided by the embodiment of the disclosure is applied, or can be preset remotely and communicate through a network. It is understood that the preset rule base may store a corresponding relationship between the type to which the exception code belongs and the processing logic, so that the processing logic corresponding to the exception code may be read from the preset rule base.
The processing logic may be a package of data and methods, and may be embodied as a segment of executable code, a function, and the like.
In a possible implementation manner, when the processing logic corresponding to the exception code does not exist in the rule base, the exception code may be sent to the exception processing center. In the exception handling center, the corresponding handling logic may be designated for the exception code by an administrator from the original handling logic, or a newly created handling logic may be assigned to the exception code. The computer to which the method provided by the embodiment of the present disclosure is applied may receive the corresponding processing logic fed back by the exception processing center for the exception code, and add the corresponding relationship between the type to which the exception code belongs and the processing logic, and the processing logic corresponding to the exception code to the rule base. The computer and the exception handling center, to which the method provided by the embodiment of the present disclosure is applied, may communicate via a network.
In step 230, the read processing logic is invoked to process the exception indicated by the exception code.
For example, for an exception code indicating that the next business segment cannot be found, the logic for handling the exception represented by the exception code may include: and automatically giving an email to the business link.
Therefore, the method provided by the embodiment of the disclosure obtains the exception code generated by the workflow, reads the processing logic corresponding to the exception code from the preset rule base, and calls the read processing logic to process the exception represented by the exception code, so as to automatically complete the processing of the exception, and the exception is not required to be manually solved, thereby achieving the purpose of improving the exception processing efficiency.
FIG. 3 is a flowchart illustrating a method of handling exceptions according to another exemplary embodiment of the present disclosure. The method may be applied to a computer 101 as shown in fig. 1. The method can comprise the following steps:
in step 310, exception codes generated by the workflow are obtained.
The exception code includes an exception source code segment and an exception type code segment, the exception source code segment is used for storing the exception source code, and the exception type code segment is used for storing the exception type code.
For example, two-segment encoding rules may be used to encode exception codes. The first section of two digits is the code section of the abnormal source, and the second section of four digits is the code section of the abnormal type. For example, the first segment has two digits, 01 represents a task instance, 02 represents a node instance, 03 represents a flow instance, 04 represents a third party application call, and so on. For another example, the second four digits, 0001, 0002, are not found by the transactor, and the like. Wherein the exception type code is used to indicate the type of exception code described herein.
In step 320, a rule base corresponding to the abnormal source code is found according to the abnormal source code stored in the abnormal source code segment of the abnormal code.
The rule base is at least two rule bases, wherein each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. For example, the exception source code 01 corresponds to a task instance exception rule base, the node instance exception rule base corresponding to 02 corresponds to a process instance exception rule base corresponding to 03, the third party application call exception rule base corresponding to 04, and the like.
In step 321, according to the abnormal type code stored in the abnormal type code segment of the abnormal code, the processing logic corresponding to the abnormal type code is read from the rule base corresponding to the abnormal source code.
For another example, if the transactor represented by the exception type code 0001 cannot find the exception, which is the node instance exception, the node instance exception rule base corresponding to the exception source code 02 includes processing logic for processing the transactor represented by the exception type code 0001 that cannot find the exception.
In step 330, the read processing logic is invoked to process the exception indicated by the exception code.
In this embodiment, the exception code includes an exception source code segment and an exception type code segment, and the rule base includes at least two rule bases, where each rule base corresponds to one exception source code and each rule base includes processing logic corresponding to different exception type codes, so that efficiency of finding the processing logic corresponding to the exception code is higher, and efficiency of processing the exception is improved.
FIG. 4 is a flowchart illustrating a method of handling exceptions according to yet another exemplary embodiment of the present disclosure. The method may be applied to a computer 101 as shown in fig. 1. The method can comprise the following steps:
in step 410, exception codes generated by the workflow are obtained.
The exception code comprises an exception grade code segment, and the exception grade code segment is used for storing exception grades.
For example, in the exception code, the exception level stored in the exception level code segment may be three levels, 01 representing a notification level, 02 representing a warning level, and 03 representing an error level.
In step 420, the processing logic corresponding to the exception code is read from a preset rule base, where the rule base includes processing logic corresponding to at least two exception codes.
In step 430, the exception codes are sorted according to the exception levels stored in the exception level code segments of the exception codes.
For example, the disclosed embodiments may preset an exception pool for storing received exception codes that have not been processed. If the exception code has been processed, the exception code is deleted from the exception code pool. After receiving the exception codes, all exception codes in the exception code pool may be sorted according to their exception code rank. And processing the abnormal codes in the abnormal code pool one by one according to the sorted sequence. It will be appreciated that different exception levels, representing different levels of importance, therefore have different priority.
In step 431, according to the sequence of the sorted exception codes, the read processing logic is invoked to process the exception represented by the exception code.
In the embodiment, the exception code comprises the exception level code segment to store the exception level, the received exception codes are sorted according to the exception level and processed according to the sorted order, so that the exception code with higher priority can be processed preferentially, and the rationality of exception processing is met.
FIG. 5 is a flowchart illustrating a method of handling exceptions according to yet another exemplary embodiment of the present disclosure. The method may be applied to a computer 101 as shown in fig. 1. The method can comprise the following steps:
in step 510, exception codes generated by the workflow are obtained.
The exception code comprises an exception source code segment, an exception type code segment and an exception grade code segment, wherein the exception source code segment is used for storing the exception source code, the exception type code segment is used for storing the exception type code, and the exception grade code segment is used for storing the exception grade.
In step 520, a rule base corresponding to the abnormal source code is found according to the abnormal source code stored in the abnormal source code segment of the abnormal code.
The rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. Each exception source code corresponds to an exception code pool.
In step 521, according to the abnormal type code stored in the abnormal type code segment of the abnormal code, the processing logic corresponding to the abnormal type code is read from the rule base corresponding to the abnormal source code.
In step 530, the exception pool corresponding to the exception source code of the exception code is found.
In step 531, the exception code and the read processing logic are sent to the exception code pool.
In step 532, the exception codes in the exception code pool are sorted according to the exception levels stored in the exception level code segments of the exception codes.
In step 533, according to the sequence of the sorted exception codes in the exception code pool, a corresponding processing logic is invoked to process the exception represented by the exception code.
In this embodiment, the exception code includes an exception source code segment, an exception type code segment, and an exception level code segment, and the rule base includes at least two rule bases, where each rule base corresponds to an exception source code and includes processing logic corresponding to different exception type codes, so that efficiency of finding the processing logic corresponding to the exception code is higher, which is beneficial to improving efficiency of processing exception and enabling the exception code with higher priority to be processed preferentially, and thus, the rationality of exception processing is satisfied.
FIG. 6 is a block diagram illustrating an apparatus 600 for handling exceptions according to an exemplary embodiment of the present disclosure. The apparatus may be configured as a computer 101 as shown in fig. 1. The apparatus may include: an acquisition module 610, a logic read module 620, and an exception handling module 630.
The obtaining module 610 may be configured to obtain exception codes generated by the workflow.
The logic reading module 620 may be configured to read processing logic corresponding to the exception code from a preset rule base, where the rule base includes processing logic corresponding to at least two exception codes.
The exception handling module 630 may be configured to invoke the read processing logic to handle the exception indicated by the exception code.
Therefore, the method provided by the embodiment of the disclosure obtains the exception code generated by the workflow, reads the processing logic corresponding to the exception code from the preset rule base, and calls the read processing logic to process the exception represented by the exception code, so as to automatically complete the processing of the exception, and the exception is not required to be manually solved, thereby achieving the purpose of improving the exception processing efficiency.
Fig. 7 is a block diagram illustrating an apparatus 600 for handling exceptions according to another exemplary embodiment of the present disclosure. In the device, the exception code includes an exception source code segment and an exception type code segment, the exception source code segment is used for storing the exception source code, and the exception type code segment is used for storing the exception type code. The rule base is at least two rule bases, wherein each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. The logic read module 620 may include: the rule base searching sub-module 621 may be configured to find out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code segment of the abnormal code. The logic reading sub-module 622 may be configured to read, according to the exception type code stored in the exception type code segment of the exception code, the processing logic corresponding to the exception type code from the rule base corresponding to the exception source code. Through the embodiment, the efficiency of searching the processing logic corresponding to the exception code is higher, and the efficiency of processing the exception is improved.
Fig. 8 is a block diagram illustrating an apparatus 600 for handling exceptions according to yet another exemplary embodiment of the present disclosure. In the device, the exception code comprises an exception level code segment, and the exception level code segment is used for storing exception levels. The exception handling module 630 may include: the sorting sub-module 631 may be configured to sort the exception codes according to their exception levels stored in their exception level code segments. The processing submodule 632 may be configured to invoke the read processing logic to process the exception represented by the exception code according to the order of the sorted exception codes. By the embodiment, the exception code with higher priority can be processed preferentially, and the rationality of exception processing is met.
Fig. 9 is a block diagram illustrating an apparatus 600 for handling exceptions according to yet another exemplary embodiment of the present disclosure. In the device, the exception code includes an exception source code segment, an exception type code segment, and an exception level code segment, where the exception source code segment is used to store the exception source code, the exception type code segment is used to store the exception type code, and the exception level code segment is used to store the exception level. The rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logic corresponding to different abnormal type codes. Each exception source code corresponds to an exception code pool. The logic read module 620 may include: the rule base searching sub-module 621 may be configured to find out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code segment of the abnormal code. The logic reading sub-module 622 may be configured to read, according to the exception type code stored in the exception type code segment of the exception code, the processing logic corresponding to the exception type code from the rule base corresponding to the exception source code. The exception handling module 630 may include: the code pool finding sub-module 633 may be configured to find an exception code pool corresponding to an exception source code of the exception code. The sending submodule 634 may be configured to send the exception code and the read processing logic to the exception code pool. The sorting sub-module 631 may be configured to sort the exception codes in the exception code pool according to the exception levels stored by the exception level code segments of the exception codes. The processing submodule 632 may be configured to invoke corresponding processing logic to process the exception represented by the exception code according to the order of the sorted exception codes in the exception code pool. Through the embodiment, the efficiency of searching the processing logic corresponding to the exception code is higher, the efficiency of processing exception is improved, the exception code with higher priority can be processed preferentially, and the rationality of exception processing is met.
In another possible implementation, when the processing logic corresponding to the exception code does not exist in the rule base, the exception code may be sent to an exception processing center. In the exception handling center, the corresponding handling logic may be designated for the exception code by an administrator from the original handling logic, or a newly created handling logic may be assigned to the exception code. For example, as shown in fig. 9, the apparatus may further include: the sending center module 601 may be configured to send the exception code to an exception handling center when the processing logic corresponding to the exception code does not exist in the rule base. A feedback receiving module 602, which may be configured to receive corresponding processing logic of the exception handling hub for the exception code feedback. A logic adding module 603 configured to add the processing logic corresponding to the exception code to the rule base.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that the various features described in the above embodiments may be combined in any suitable manner without departing from the scope of the invention. In order to avoid unnecessary repetition, various possible combinations will not be separately described in this disclosure.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.
Claims (6)
1. A method of handling exceptions, comprising:
acquiring an exception code generated by a workflow;
reading processing logic corresponding to the abnormal codes from a preset rule base, wherein the rule base comprises the processing logic corresponding to at least more than two abnormal codes;
calling the read processing logic to process the exception represented by the exception code;
the exception code comprises an exception source code section and an exception grade code section, wherein the exception source code section is used for storing exception source codes, and the exception grade code section is used for storing exception grades; each abnormal source code corresponds to an abnormal code pool;
the calling the read processing logic to process the exception represented by the exception code comprises:
finding out an abnormal code pool corresponding to an abnormal source code of the abnormal code;
sending the exception code and the read processing logic to the exception code pool;
sorting the abnormal codes in the abnormal code pool according to the abnormal grade stored in the abnormal grade code segment of the abnormal code;
and calling corresponding processing logic to process the exception represented by the exception code according to the sequence of the sequenced exception code in the exception code pool.
2. The method of claim 1, wherein the exception code further comprises an exception type code segment, and wherein the exception type code segment is used for storing an exception type code; the rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logics corresponding to different abnormal type codes;
the processing logic for reading the exception code from the preset rule base includes:
finding out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code section of the abnormal code;
and reading the processing logic corresponding to the abnormal type code from the rule base corresponding to the abnormal source code according to the abnormal type code stored in the abnormal type code segment of the abnormal code.
3. The method of claim 1, further comprising:
when the processing logic corresponding to the abnormal code does not exist in the rule base, the abnormal code is sent to an abnormal processing center;
receiving corresponding processing logic fed back by the exception processing center for the exception code;
and adding the processing logic corresponding to the abnormal code into the rule base.
4. An apparatus for handling exceptions, comprising:
the acquisition module is configured to acquire an exception code generated by the workflow;
the logic reading module is configured to read processing logic corresponding to the abnormal code from a preset rule base, wherein the rule base comprises the processing logic corresponding to at least two abnormal codes;
the exception handling module is configured to call the read processing logic to handle the exception represented by the exception code;
the exception code comprises an exception source code section and an exception grade code section, wherein the exception source code section is used for storing exception source codes, and the exception grade code section is used for storing exception grades; each abnormal source code corresponds to an abnormal code pool;
the exception handling module comprises:
the code pool searching submodule is configured to search an abnormal code pool corresponding to an abnormal source code of the abnormal code;
a sending submodule configured to send the exception code and the read processing logic to the exception code pool;
the sorting submodule is configured to sort the abnormal codes in the abnormal code pool according to the abnormal levels stored in the abnormal level code segments of the abnormal codes;
and the processing submodule is configured to call corresponding processing logic to process the exception represented by the exception code according to the sequence of the sequenced exception code in the exception code pool.
5. The apparatus of claim 4, wherein the exception code further comprises an exception type code segment, and wherein the exception type code segment is configured to store an exception type code; the rule base is at least two rule bases, each rule base corresponds to one abnormal source code, and each rule base comprises processing logics corresponding to different abnormal type codes;
the logic read module comprises:
the rule base searching submodule is configured to search out a rule base corresponding to the abnormal source code according to the abnormal source code stored in the abnormal source code segment of the abnormal code;
and the logic reading submodule is configured to read processing logic corresponding to the abnormal type code from a rule base corresponding to the abnormal source code according to the abnormal type code stored in the abnormal type code segment of the abnormal code.
6. The apparatus of claim 4, further comprising:
the sending center module is configured to send the abnormal code to an abnormal processing center when the processing logic corresponding to the abnormal code does not exist in the rule base;
a feedback receiving module configured to receive corresponding processing logic of the exception processing center for the exception code feedback;
and the logic adding module is configured to add the processing logic corresponding to the abnormal code to the rule base.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610850344.0A CN106648944B (en) | 2016-09-26 | 2016-09-26 | Method and device for processing exception |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610850344.0A CN106648944B (en) | 2016-09-26 | 2016-09-26 | Method and device for processing exception |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106648944A CN106648944A (en) | 2017-05-10 |
| CN106648944B true CN106648944B (en) | 2020-04-17 |
Family
ID=58854030
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610850344.0A Active CN106648944B (en) | 2016-09-26 | 2016-09-26 | Method and device for processing exception |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106648944B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107704484B (en) * | 2017-07-25 | 2020-06-19 | 深圳壹账通智能科技有限公司 | Webpage error information processing method and device, computer equipment and storage medium |
| CN107515798A (en) * | 2017-09-06 | 2017-12-26 | 郑州云海信息技术有限公司 | The error handling method and device of storage management software |
| CN108595557A (en) * | 2018-04-11 | 2018-09-28 | 浙江大学 | A kind of workflow executing method for flexible process |
| CN109358572A (en) * | 2018-09-26 | 2019-02-19 | 深圳壹账通智能科技有限公司 | Method, apparatus, computer equipment and the storage medium of machinery equipment O&M |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101765135A (en) * | 2010-01-19 | 2010-06-30 | 北京千禧维讯科技有限公司 | Method for monitoring fault processing network of telecommunication equipment |
| CN102740160A (en) * | 2011-03-31 | 2012-10-17 | 青岛海信电器股份有限公司 | Method and apparatus for recording failures of television software |
| CN103618297A (en) * | 2013-07-17 | 2014-03-05 | 国家电网公司 | High-efficiency and high-reliability fault processing method aiming at complex power distribution network |
| CN103674590A (en) * | 2013-11-09 | 2014-03-26 | 皖江新兴产业技术发展中心 | Automatic alarm system implementation method of semiconductor chip full-automatic packaging equipment |
| CN103838637A (en) * | 2014-03-03 | 2014-06-04 | 江苏智联天地科技有限公司 | Terminal automatic fault diagnosis and restoration method on basis of data mining |
-
2016
- 2016-09-26 CN CN201610850344.0A patent/CN106648944B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101765135A (en) * | 2010-01-19 | 2010-06-30 | 北京千禧维讯科技有限公司 | Method for monitoring fault processing network of telecommunication equipment |
| CN102740160A (en) * | 2011-03-31 | 2012-10-17 | 青岛海信电器股份有限公司 | Method and apparatus for recording failures of television software |
| CN103618297A (en) * | 2013-07-17 | 2014-03-05 | 国家电网公司 | High-efficiency and high-reliability fault processing method aiming at complex power distribution network |
| CN103674590A (en) * | 2013-11-09 | 2014-03-26 | 皖江新兴产业技术发展中心 | Automatic alarm system implementation method of semiconductor chip full-automatic packaging equipment |
| CN103838637A (en) * | 2014-03-03 | 2014-06-04 | 江苏智联天地科技有限公司 | Terminal automatic fault diagnosis and restoration method on basis of data mining |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106648944A (en) | 2017-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106648944B (en) | Method and device for processing exception | |
| US10108415B2 (en) | Maintaining the integrity of process conventions within an ALM framework | |
| CN108108436B (en) | Data storage method and device, storage medium and electronic equipment | |
| CN111090582A (en) | Error code positioning method and device, storage medium and electronic equipment | |
| CN113283917A (en) | Quality tracing method and device for engineering raw materials | |
| CN111581211B (en) | Data table updating method, device, equipment and computer readable storage medium | |
| CN111641734A (en) | Node identifier generation method, device and storage medium | |
| US10620950B2 (en) | Message parsing in a distributed stream processing system | |
| CN107172113B (en) | Processing method and device in abnormal service call | |
| CN112685107A (en) | Workflow engine-based operation processing method, engine, electronic device and medium | |
| US20200042296A1 (en) | Code lineage tool | |
| CN113468446B (en) | Method, system and equipment for supporting identification of third party two-dimensional code data | |
| CN115496470A (en) | Full-link configuration data processing method and device and electronic equipment | |
| CN110765196A (en) | Method and equipment for generating and executing ETL task | |
| CN111488117A (en) | Method, electronic device, and computer-readable medium for managing metadata | |
| CN112507014B (en) | Data storage method, device and system based on credible account book database | |
| CN115826980A (en) | Data processing method, data processing device, storage medium and electronic equipment | |
| CN114021133A (en) | Code processing method and device, electronic equipment and storage medium | |
| CN111309727B (en) | Information table processing method, device and storage medium | |
| CN114493799A (en) | Method and system for managing special vehicle order data in warehouse and table dividing manner | |
| CN114493305A (en) | Industrial equipment management method and equipment based on identification analysis and storage medium | |
| CN114519047A (en) | Identification resolution gateway-based data knowledge base management method and equipment | |
| CN110196793B (en) | Log analysis method and device for plug-in database | |
| CN113094574A (en) | Information query method and device, electronic equipment and readable storage medium | |
| CN110825606B (en) | Data operation method, device and central station system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |