CN117112368B - Abnormality processing method, abnormality processing device, electronic equipment and storage medium - Google Patents
Abnormality processing method, abnormality processing device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117112368B CN117112368B CN202311348624.8A CN202311348624A CN117112368B CN 117112368 B CN117112368 B CN 117112368B CN 202311348624 A CN202311348624 A CN 202311348624A CN 117112368 B CN117112368 B CN 117112368B
- Authority
- CN
- China
- Prior art keywords
- target
- error code
- abnormal
- processing
- error
- 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
- 238000012545 processing Methods 0.000 title claims abstract description 256
- 230000005856 abnormality Effects 0.000 title claims description 28
- 238000003672 processing method Methods 0.000 title description 3
- 230000002159 abnormal effect Effects 0.000 claims abstract description 136
- 238000000034 method Methods 0.000 claims abstract description 102
- 230000008569 process Effects 0.000 claims abstract description 52
- 238000012800 visualization Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 6
- 230000000007 visual effect Effects 0.000 abstract description 28
- 230000010485 coping Effects 0.000 abstract 1
- 238000011160 research Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000011835 investigation Methods 0.000 description 3
- RYYVLZVUVIJVGH-UHFFFAOYSA-N caffeine Chemical compound CN1C(=O)N(C)C(=O)C2=C1N=CN2C RYYVLZVUVIJVGH-UHFFFAOYSA-N 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- LPHGQDQBBGAPDZ-UHFFFAOYSA-N Isocaffeine Natural products CN1C(=O)N(C)C(=O)C2=C1N(C)C=N2 LPHGQDQBBGAPDZ-UHFFFAOYSA-N 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 229960001948 caffeine Drugs 0.000 description 1
- VJEONQKOZGKCAK-UHFFFAOYSA-N caffeine Natural products CN1C(=O)N(C)C(=O)C2=C1C=CN2C VJEONQKOZGKCAK-UHFFFAOYSA-N 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000011112 process operation Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- 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/079—Root cause analysis, i.e. error or fault diagnosis
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention relates to the technical field of computers, and provides an exception handling method, an exception handling device, electronic equipment and a storage medium, wherein the exception handling method comprises the following steps: responding to a service processing request carrying the current language environment, and acquiring the abnormal information comprising the target abnormal error code in the service processing process; determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance in a visualized manner; and performing exception handling on the target exception error code by using a target error code handling strategy. According to the invention, by adopting the mode of distributing the error code processing strategy adopted by the visual configuration of the different abnormal error codes in different language environments, only the visual configuration information is required to be called for coping with the language environment demands of the delivery user, the purpose of flexibly determining the error code processing strategy according to different language environments is realized, the unified abnormal processing efficiency is improved, and the abnormal processing difficulty is reduced.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to an exception handling method, an exception handling device, an electronic device, and a storage medium.
Background
During the running process of enterprise application, no matter whether the normal business logic check is not passed or the program has the factors of Bug, unstable server or unstable network, etc., the abnormality is unavoidable; regardless of the occurrence of an exception for any of the reasons described above, it is desirable to determine a processing policy to handle the exception. Therefore, how to uniformly process the anomalies occurring in the running process of enterprise applications becomes a key problem to be solved currently.
In the related art, the processing strategy of the error code is defined by defining hard coding modes such as error code constant or configuration file, and the language environment of the error code constant is defined in the configuration file, so that for the exception occurring in the enterprise operation process, the processing strategy for solving the exception is searched from the defined processing strategy, and the exception is processed by using the processing strategy.
However, since the language environment defined by the hard coding mode is fixed, the processing strategy of processing the exception by using the fixed language environment is also fixed, when the language environment required by the delivering user is different from the defined language environment, the research personnel are required to intervene in re-writing codes and re-publishing the codes, and the defined error code constants are increased, so that the efficiency of uniformly processing the exception is low and the difficulty is high.
Disclosure of Invention
The present invention is directed to solving at least one of the technical problems existing in the related art. Therefore, the invention provides an exception handling method, by means of the mode of distributing the error code handling strategies adopted by the visualized configuration of different error codes in different language environments, the language environment requirements of delivery users can be met without intervention of research personnel, only the visualized configuration information is required to be called or the visualized configuration is required to be modified, and excessive error code constants are not required to be defined, so that the purpose of flexibly determining different error code handling strategies for handling the abnormal error codes according to different language environments is realized, the unified exception handling efficiency is improved, and the exception handling difficulty is greatly reduced.
The invention also provides an exception handling device.
The invention further provides electronic equipment.
The invention also proposes a non-transitory computer readable storage medium.
An exception handling method according to an embodiment of the first aspect of the present invention includes:
responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the anomaly information comprises a target anomaly error code;
determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance in a visualized manner;
And carrying out exception handling on the target exception error code by utilizing the target error code handling strategy.
According to the exception handling method of the embodiment of the invention, when responding to the service handling request carrying the current language environment, firstly, the exception information in the service handling process is acquired, and under the condition that the exception information comprises the target exception error code, the target error code handling strategy for handling the target exception code based on the current language environment is determined from the error code handling strategies adopted for handling the different exception codes under the different language environments configured in advance in a visualized manner, so that the target exception code handling strategy is convenient for carrying out exception handling on the target exception code. In this way, by means of the error code processing strategy adopted by the distributed visual configuration for processing different abnormal error codes in different language environments, the language environment requirement of the delivering user can be met without the intervention of research personnel, only the visual configuration information is required to be called or the visual configuration is required to be modified, and excessive error code constants are not required to be defined, so that the purpose of flexibly determining different error code processing strategies for processing the abnormal error codes according to different language environments is realized, the unified processing efficiency of the abnormal is improved, and the abnormal processing difficulty is greatly reduced.
According to an embodiment of the present invention, the exception information further includes a target access parameter and a target error stack associated with the target exception error code, and before determining, in the error code processing policy adopted for processing different exception error codes in the different language environments configured from the pre-visualization, the target error code processing policy adopted for processing the target exception error code in the current language environment, the method further includes:
determining a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack, wherein the target error code configuration file comprises an error code processing strategy adopted for processing the target abnormal error code under different language environments.
According to one embodiment of the present invention, the determining a target error code configuration file including the target exception error code, the target access parameter, and the target error stack includes:
searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a cache;
and searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a database based on the unsearched result.
According to one embodiment of the present invention, the searching the target error code configuration file including the target abnormal error code, the target access parameter and the target error stack from the cache includes:
searching a target error code configuration file comprising the target error code, the target access parameter and the target error stack from a first-level cache based on the abnormal type of the target error code; the first-level cache is used for temporarily storing a plurality of first error code configuration files, wherein the plurality of first error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of non-business abnormal types under different language environments;
searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a second-level cache based on the result which is not searched in the first-level cache; the second-level cache is used for temporarily storing a plurality of second error code configuration files, wherein the plurality of second error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of abnormal business types under different language environments.
According to one embodiment of the invention, the method further comprises:
acquiring call chain information corresponding to the service processing request;
and determining error code log information based on the call chain information and the target error code processing strategy, and carrying out log record on the error code log information.
According to one embodiment of the present invention, the determining process of the service processing request carrying the current language environment includes:
responding to an initial service processing request initiated by a client;
and identifying the current language environment from the initial service processing request, and binding the identified current language environment with the initial service processing request to obtain the service processing request carrying the current language environment.
According to one embodiment of the invention, the method further comprises:
and feeding back an exception processing result to the client based on a feedback mode of the pre-visualization configuration.
An exception handling apparatus according to an embodiment of a second aspect of the present invention includes:
the abnormal response module is used for responding to the service processing request carrying the current language environment and acquiring abnormal information in the service processing process; the anomaly information comprises a target anomaly error code;
The strategy determining module is used for determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance;
and the exception handling module is used for carrying out exception handling on the target exception error code by utilizing the target error code handling strategy.
According to the exception handling device provided by the embodiment of the invention, when responding to a service handling request carrying a current language environment, firstly, the exception information in the service handling process is acquired, and under the condition that the exception information comprises target exception error codes, the target error code handling strategy for handling the target exception codes based on the current language environment is determined from the error code handling strategies adopted for handling the different exception codes under different language environments configured in advance, so that the target exception codes are conveniently and abnormally handled by using the target error code handling strategy. In this way, by means of the error code processing strategy adopted by the distributed visual configuration for processing different abnormal error codes in different language environments, the language environment requirement of the delivering user can be met without the intervention of research personnel, only the visual configuration information is required to be called or the visual configuration is required to be modified, and excessive error code constants are not required to be defined, so that the purpose of flexibly determining different error code processing strategies for processing the abnormal error codes according to different language environments is realized, the unified processing efficiency of the abnormal is improved, and the abnormal processing difficulty is greatly reduced.
The above technical solutions in the embodiments of the present invention have at least one of the following technical effects: when responding to a service processing request carrying a current language environment, firstly acquiring exception information in a service processing process, and determining a target error code processing strategy for processing the target exception error code based on the current language environment from error code processing strategies adopted by processing different exception error codes in different language environments configured in advance under the condition that the exception information comprises the target exception error code, so as to facilitate exception processing of the target exception error code by utilizing the target error code processing strategy. In this way, by means of the error code processing strategy adopted by the distributed visual configuration for processing different abnormal error codes in different language environments, the language environment requirement of the delivering user can be met without the intervention of research personnel, only the visual configuration information is required to be called or the visual configuration is required to be modified, and excessive error code constants are not required to be defined, so that the purpose of flexibly determining different error code processing strategies for processing the abnormal error codes according to different language environments is realized, the unified processing efficiency of the abnormal is improved, and the abnormal processing difficulty is greatly reduced.
Furthermore, the internationalization support purpose and the purpose of supporting enterprise application under different language environments can be achieved by determining the target error code configuration file comprising the target error code, the target access parameter and the target error stack, and then determining the target error code processing strategy for processing the target error code under the current language environment.
Furthermore, by searching the target error code configuration file from the cache first and searching the target error code configuration file from the database when the cache is not hit, not only can the exception handling performance be improved, but also the flexibility and reliability of determining the target error code configuration file can be improved, and meanwhile, the exception handling efficiency can also be improved.
Furthermore, the target error code configuration files are queried step by step in a mode of respectively caching the error code configuration files corresponding to the abnormal types by a hierarchical caching technology, so that the flexibility and the reliability of querying the target error code configuration files can be improved by combining the abnormal classification and the hierarchical caching technology, and the efficiency and the performance of querying the target error code configuration files can be improved.
Still further, by determining a target error code processing strategy, the method of determining error code log information by combining with corresponding call chain information to perform log recording ensures that errors can be rapidly and accurately positioned when the errors are subsequently checked and re-recorded, thereby greatly reducing the difficulty of the errors of the subsequent checking and re-recorded and improving the efficiency of solving the problems.
Furthermore, the feedback of the abnormal processing result is correspondingly delivered to the client by the feedback mode of the pre-visualization configuration, so that the prompt document displayed by the client can be ensured to be more visual and clear, and meanwhile, the flexibility of interaction between the client and the server is improved.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the related art, the drawings that are required to be used in the embodiments or the related technical descriptions will be briefly described, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is a flow chart of an exception handling method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a data interaction flow of an exception handling system according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an exception handling apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
In the running process of enterprise application, whether normal business logic verification is not passed or the program has the factors of Bug, unstable server or unstable network, etc., errors and anomalies are unavoidable; common error occurrence scenarios include:
(1) Business operations are limited: preventing the operation illegal business operation from causing negative effects on the system, such as unauthorized operation, insufficient participation activity conditions, insufficient commodity inventory, etc.;
(2) Operating environment anomalies: environmental impact such as database downtime, unavailability of third party service interfaces, network instability, service flow control, call chain fusing, etc. is difficult to predict;
(3) Program bug: the developer considers that the problem is that errors, such as null pointers, array out-of-bounds and the like, are thrown in the running process of the program.
Regardless of the exception that occurs for any of the reasons described above, a large stack of error stack information cannot be fed back directly to the client, and instead, a processing policy for handling the exception needs to be determined. Therefore, how to uniformly process the anomalies occurring in the running process of enterprise applications becomes a key problem to be solved currently.
In the related art, the processing strategy of the error code is defined by defining hard coding modes such as error code constant or configuration file, and the language environment of the error code constant is defined in the configuration file, so that for the exception occurring in the enterprise operation process, the processing strategy for solving the exception is searched from the defined processing strategy, and the exception is processed by using the processing strategy.
However, since the language environment defined by the hard coding mode is fixed, the processing strategy of processing the exception by using the fixed language environment is also fixed, when the language environment required by the delivering user is different from the defined language environment, the research personnel are required to intervene in re-writing codes and re-publishing the codes, and the defined error code constants are increased, so that the efficiency of uniformly processing the exception is low and the difficulty is high.
In order to solve the above technical problems, the present invention provides an anomaly handling method, an anomaly handling device, an electronic device, and a storage medium. The exception handling method, the device, the electronic equipment and the storage medium provided by the invention are described below with reference to fig. 1-4, wherein an execution main body of the exception handling method can be a server, the server can be a targeted service program, a computer running the server is called a server, the server can be a server, a server cluster formed by a plurality of servers, a cloud computing center and the like; also, the abnormality processing method may be applied to an abnormality processing apparatus provided in a server, which may be realized by software, hardware, or a combination of both. The exception handling method will be described below by taking the execution subject of the exception handling method as a server as an example.
In order to facilitate understanding of the exception handling method provided by the embodiments of the present invention, the exception handling method provided by the present invention will be described in detail by the following several exemplary embodiments. It is to be understood that the following several exemplary embodiments may be combined with each other and that some embodiments may not be repeated for the same or similar concepts or processes.
Referring to fig. 1, a flow chart of an exception handling method provided by the present invention is shown in fig. 1, and the exception handling method includes the following steps 110 to 130.
Step 110, responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the anomaly information includes a target anomaly error code.
The current language environment may include, but is not limited to, one of a chinese language environment, an english language environment, a japanese language environment, and a korean language environment, and the service processing request may be a processing request that is automatically generated when the user inputs a normal service operation at the client, where the current language environment is a language environment used when the user inputs the normal service operation at the client. The number of service processing requests may be 1 or more. In addition, the target abnormal error code is a unique identification of the error type of the error generated in the service processing process, and has specific analysis rules, namely specific error code processing strategies, for both service and non-service errors.
Specifically, when the server responds to a service processing request carrying a current language environment, corresponding service processing is performed, whether errors occur is monitored in the service processing process, so that abnormal information automatically generated when errors occur in the service processing process is acquired, the quantity of the abnormal information is related to the quantity of the errors occurring in the execution process, for example, when errors occur once in the service processing process, abnormal information is correspondingly generated, and a target abnormal error code is correspondingly generated.
And 120, determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments of the pre-visualization configuration.
Specifically, the server develops a visual configuration page, and a service personnel can pre-configure error code processing strategies adopted by processing different abnormal error codes in different language environments through the visual configuration page, so that each abnormal error code can correspond to the error code processing strategies in a plurality of language environments; based on the above, when the target abnormal error code is acquired, an error code processing strategy for processing the target abnormal error code based on the current language environment can be rapidly determined based on the visual configuration result.
And 130, performing exception handling on the target exception error code by using a target error code handling strategy.
Specifically, when the server determines a target error code processing policy adopted for processing a target error code in the current language environment, the target error code processing policy may be utilized to perform exception processing on the target error code, where the exception processing may specifically be: under the current language environment, processing errors generated in a business processing process by using a target error code processing strategy; further, when there are multiple target error code processing strategies, it can be determined that multiple errors occur in the service processing process, and at this time, each target error code processing strategy can be used to process the corresponding errors occurring in the service processing process.
When responding to a service processing request carrying a current language environment, the exception information in the service processing process is firstly obtained, and under the condition that the exception information comprises target exception error codes, a target error code processing strategy for processing the target exception error codes based on the current language environment is determined from error code processing strategies adopted for processing the different exception error codes in different language environments configured in advance, so that the target exception error codes are conveniently processed by the target error code processing strategy. In this way, by means of the error code processing strategy adopted by the distributed visual configuration for processing different abnormal error codes in different language environments, the language environment requirement of the delivering user can be met without the intervention of research personnel, only the visual configuration information is required to be called or the visual configuration is required to be modified, and excessive error code constants are not required to be defined, so that the purpose of flexibly determining different error code processing strategies for processing the abnormal error codes according to different language environments is realized, the unified processing efficiency of the abnormal is improved, and the abnormal processing difficulty is greatly reduced.
It can be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, an error code configuration file including key feature information such as an exception error code, an access parameter, and an error stack may be configured according to different exception error codes during the visual configuration, and then a required error code handling policy may be determined from the error code configuration file. Based on this, in the case that the exception information further includes the target access parameter and the target error stack associated with the target exception code, before step 120, the exception handling method provided by the present invention may further include:
determining a target error code configuration file comprising a target abnormal error code, a target access parameter and a target error stack, wherein the target error code configuration file comprises an error code processing strategy adopted for processing the target abnormal error code under different language environments.
The target access parameter may include, but is not limited to, an input/output parameter associated with a target abnormal error code, that is, an input/output parameter corresponding to an error occurring in a service processing process.
Specifically, for a visual configuration page developed by a server, when a service person can configure an error code processing strategy adopted for processing different abnormal error codes in different language environments through the visual configuration page, initial error code configuration files comprising key characteristic information such as the abnormal error codes, access parameters, error stacks and the like can be configured first, and the number of the initial error code configuration files is the same as that of the abnormal error codes; and then, configuring error code processing strategies adopted for processing corresponding abnormal error codes in different language environments in each initial error code configuration file, so as to obtain a plurality of error code configuration files. Based on the above, when the exception information in the service processing process is obtained, a target error code configuration file including a target exception code, a target access parameter and a target error stack which are matched in the plurality of error code configuration files can be matched based on the target exception code, the target access parameter and the target error stack which are included in the exception information, and then, from error code processing strategies adopted for processing different exception codes in different language environments included in the target error code configuration file, a target error code processing strategy adopted for processing the target exception code in the current language environment is determined.
It should be noted that, if the target error code processing policy of the current language environment for processing the target abnormal error code is not queried from the target error code configuration file, the preset default error code processing policy may be determined as the target error code processing policy.
The exception handling method provided by the invention can realize internationalization support purposes and support the purposes of running enterprise applications under different language environments by firstly determining the target error code configuration file comprising the target exception code, the target access parameter and the target error stack and then determining the target error code processing strategy for processing the target exception code under the current language environment, and ensures that service development can take effect in real time without paying attention to an exception handling mechanism by defining and uniformly processing the target error code configuration file in visual configuration, thereby improving the flexibility and applicability of global handling of various exceptions.
It will be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, in order to improve the exception handling performance, the error code configuration file configured in advance may be temporarily stored in the cache and stored in the database for a long period of time, so as to facilitate subsequent querying from the cache and querying from the database for the required target error code configuration file when the cache is missed. Based on this, a target error code configuration file including a target exception error code, a target access parameter, and a target error stack is determined, and the specific implementation process may include:
Firstly, searching a target error code configuration file comprising a target abnormal error code, a target access parameter and a target error stack from a cache; and searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from the database based on the unsearched result.
Specifically, by configuring an error code processing strategy adopted by a visual configuration page developed by a server for processing different abnormal error codes in different language environments, a service side can obtain a plurality of error code configuration files, each error code configuration file comprises key characteristic information such as a corresponding abnormal error code, a corresponding access parameter, a corresponding error stack and the like, and the obtained plurality of error code configuration files can be temporarily stored in a cache. Based on the above, when the exception information in the business processing process is acquired, the target error code configuration file including the target exception code, the target access parameter and the target error stack can be queried from the cache based on the key feature information in the exception information.
When the target error code configuration file is queried from the cache, determining the target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack; when the target error code configuration file is not queried from the cache, the target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack can be queried from the database, and the target error code configuration file queried from the database is determined.
It should be noted that, considering that the target error code configuration file which is not queried from the cache is automatically deleted when the temporary storage time length arrives, that is, the temporary storage is expired, so that the cache is not hit, when the target error code configuration file can be queried from the database, the queried target error code configuration file is temporarily stored in the cache; so that subsequent direct hits from the cache can be made.
According to the exception handling method provided by the invention, the mode of searching the target error code configuration file from the cache firstly and searching the target error code configuration file from the database when the cache is not hit can not only improve the exception handling performance, but also improve the flexibility and reliability of determining the target error code configuration file, and simultaneously improve the exception handling efficiency.
It may be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, it is considered that the caches may store error code configuration files of different exception types in a hierarchical manner, so that the target error code configuration files may be searched for in a manner of sequentially querying each level of cache. Based on this, the target error code configuration file matched with the abnormal error code, the access parameter and the error stack is queried from the cache, and the specific implementation process may include:
Searching a target error code configuration file comprising a target error code, a target access parameter and a target error stack from a first-level cache based on the abnormal type of the target error code; the first-level cache is used for temporarily storing a plurality of first error code configuration files, wherein the plurality of first error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of non-business abnormal types under different language environments; searching a target error code configuration file comprising a target abnormal error code, a target access parameter and a target error stack from the second-level cache based on a result which is not searched in the first-level cache; the second-level cache is used for temporarily storing a plurality of second error code configuration files, wherein the plurality of second error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of abnormal business types under different language environments.
The non-business exception types may include, but are not limited to, space pointer exceptions, connection exceptions, structured query language (Structured Query Language, SQL) database exceptions, other exceptions, and the like, caused by database downtime, network instability, and the like. Further, a level one cache may refer to a process level cache, storing access intra-process operations, such as a cache like ehcache, caffeine. By way of example, the non-business exception type may be an unknown exception during system operation, such as a network connection timeout, program operation array out of range, etc.
Further, the business anomaly types may include, but are not limited to, inventory shortage anomalies thrown during the running process of the program due to the fact that the developer is not considering the situation, record repetition anomalies, general business anomalies and the like. Further, a secondary cache may refer to a centralized cache, such as Redis, that is shared with processes. By way of example, the business anomalies may be anomalies defined based on business rules, such as inventory deductions insufficient to drop out restrictions, anomalies that drop out to prevent operation from continuing, anomalies that engage in activity unsatisfactory to drop out, and resources outside of unauthorized access rights, etc.
Specifically, in the case that the server temporarily stores a plurality of first error code configuration files belonging to a non-service exception type in a first-level cache and a plurality of second error code configuration files belonging to a service exception type in a second-level cache, among a plurality of error code configuration files obtained through visual configuration, the server may query a target error code configuration file from the first-level cache first, and when the target error code configuration file is queried from the first-level cache, the target error code configuration file is determined; otherwise, when the target error code configuration file is not queried from the first-level cache, querying the target error code configuration file from the second-level cache; when the target error code configuration file is queried from the secondary cache, namely, the target error code configuration file is determined by querying the hierarchical cache.
According to the exception handling method provided by the invention, the flexibility of the cache is improved by inquiring the target error code configuration file from the part of error code configuration files which are temporarily stored in the first-level cache and belong to the non-business exception type, and the flexibility and the reliability of inquiring the target error code configuration file can be further improved by combining the exception classification and the cache technology.
According to the exception handling method provided by the invention, the target error code configuration files are queried step by step in a mode of respectively caching the error code configuration files corresponding to the exception types by the hierarchical caching technology, so that the flexibility and the reliability of querying the target error code configuration files can be improved by combining the exception classification and the hierarchical caching technology, and the efficiency and the performance of querying the target error code configuration files can be improved.
It can be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, it is considered that if each error in the execution process of the service processing request is not recorded in time, the difficulty of subsequent investigation and recovery of the error is increased, and the problem solving efficiency is reduced. Based on this, the exception handling method provided by the present invention may further include:
Firstly, acquiring call chain information corresponding to a service processing request; and determining error code log information based on the call chain information and the target error code processing strategy, and performing log record on the error code log information.
The call chain information may include information of each link that the service processing request passes through in the execution process, and the call chain information may be specifically a call link identification number (Identity document, ID).
Specifically, under the condition that a target error code processing strategy for processing a target abnormal error code in a current language environment is determined, the determined target error code processing strategy can be analyzed first to obtain call chain information corresponding to a service processing request, error code log information is built further based on the call chain information corresponding to the service processing request and the target error code processing strategy, namely, after the call chain information and the target error code processing strategy are integrated in a log form, error code log information can be obtained, and log recording is carried out on the error code log information.
According to the exception handling method provided by the invention, through determining one target error code handling strategy, the mode of determining the error code log information by combining the corresponding call chain information to perform log record is combined, so that the errors can be rapidly and accurately positioned during subsequent investigation and multi-disc errors, the difficulty of the subsequent investigation and multi-disc errors is greatly reduced, and the problem solving efficiency is improved.
It may be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, considering that a request initiated by a client does not generally carry a language environment, a service end may determine a service processing request carrying a current language environment by performing language environment identification on the request initiated by the client through a preset error code interceptor and then binding the request to a request context. Based on this, the determining procedure of the service processing request carrying the current language environment in step 110 may specifically include:
firstly, responding to an initial service processing request initiated by a client; and further identifying the current language environment from the initial service processing request, and binding the identified current language environment with the initial service processing request to obtain the service processing request carrying the current language environment.
The client may be used to automatically generate an initial service processing request when the user inputs normal service operation, the client may be an application program for providing local service for the user, and the client may run on an electronic device, where the electronic device may be a personal computer (Personal Computer, PC), a portable device, a notebook computer, a smart phone, a tablet computer, a portable wearable device, and other electronic devices.
Specifically, an error code interceptor is arranged in the server, when the delivery user inputs normal service operation at the client, the server can perform pre-processing on the error code interceptor, such as the error code interceptor is effective, intercepting an initial service processing request initiated by the client, performing language environment recognition on the intercepted initial service processing request to recognize a current language environment, and binding the recognized current language environment with the initial service processing request, thereby obtaining the service processing request carrying the current language environment.
According to the exception handling method provided by the invention, the server side obtains the service handling request carrying the current language environment by identifying the current language environment from the initial service handling request initiated by the client side and then binding the current language environment with the initial service handling request. In this way, the error code processing strategy which is determined later can be ensured to also support the current language environment, so that the whole exception processing process is ensured to be more semantic and personalized.
It may be appreciated that, based on the exception handling method shown in fig. 1, in an exemplary embodiment, in order to ensure that the corresponding user of the client can timely and intuitively learn the exception handling result, the exception handling result may be individually fed back to the client. Based on this, the exception handling method provided by the present invention may further include:
And feeding back an exception processing result to the client based on a feedback mode of the pre-visualization configuration.
The feedback mode may include, but is not limited to, one of short messages, mails, instant messaging software, and other modes.
Specifically, when the service personnel configures the feedback mode on the visual configuration page developed by the server in advance, the exception handling result obtained after the exception handling of the exception error code by using the error code handling policy can be used to facilitate the corresponding delivery of the prompt document of the user feedback exception handling result to the client through the feedback mode of the visual configuration in advance.
It should be noted that, when the service personnel configures the alarm level on the visual configuration page developed by the server in advance, the user feedback exception handling result can be correspondingly delivered to the client, and the corresponding alarm level can be also fed back at the same time; the pre-configured alarm level may include, but is not limited to, a normal level and an emergency level, and the corresponding exception handling result may be configured for the normal level without notifying a technical responsible person, and the corresponding exception handling result may be configured for the emergency level without immediately notifying the technical responsible person, and the notification manner may also include, but is not limited to, one of a short message, a mail, instant messaging software, and other manners.
According to the exception handling method provided by the invention, the exception handling result is fed back to the corresponding delivery user of the client through the feedback mode of the pre-visualization configuration, so that the prompt document displayed by the client can be ensured to be more visual and clear, and meanwhile, the flexibility of interaction between the client and the server is improved.
For example, referring to the data interaction flow diagram of the exception handling system shown in fig. 2, as shown in fig. 2, the server may set a service processing center, a rule storage center and an error log storage service center in addition to the error code interceptor, where the service processing center is configured to execute a service processing request carrying the current language environment, generate exception information when an error occurs in the service processing process, send the exception information to the error code interceptor, and the error code interceptor is configured to parse the exception information, extract key feature information such as a target exception error code, a target access parameter and a target error stack, and send the extracted key feature information to the rule storage center; the rule storage center is used for sequentially inquiring the target error code configuration files comprising the target abnormal error code, the target access parameter and the target error stack from the first-level cache and the second-level cache based on the received key feature information, inquiring the target error code configuration files comprising the target abnormal error code, the target access parameter and the target error stack from the database when the first-level cache and the second-level cache are not hit, and caching the inquired target error code configuration files, namely storing the inquired target error code configuration files into corresponding level caches according to the abnormal types of the target abnormal error codes; in addition, the error code interceptor is also used for analyzing the determined target error code processing strategy to obtain calling chain information corresponding to the service processing request, constructing error code log information based on the calling chain information and the target error code processing strategy, and reporting the constructed error code log information to an error log storage service center in an asynchronous mode; the error code interceptor is also used for feeding back an exception handling result to the corresponding delivery user of the client; the error log storage service center is used for monitoring the error code log information and storing the monitored error code log information so as to develop the quick positioning problem. The specific processes involved therein can be found in the foregoing embodiments. And will not be described in detail herein.
Referring to fig. 3, a schematic structural diagram of an exception handling apparatus according to the present invention is shown in fig. 3, and the exception handling apparatus 300 includes: an exception response module 310, a policy determination module 320, and an exception handling module 330.
An exception response module 310, configured to obtain exception information in a service processing process in response to a service processing request carrying a current language environment; the anomaly information includes a target anomaly error code.
The policy determining module 320 is configured to determine, from the error code processing policies adopted for processing different abnormal error codes in different language environments configured in advance, a target error code processing policy adopted for processing a target abnormal error code in the current language environment.
The exception handling module 330 is configured to perform exception handling on the target exception error code by using a target error code handling policy.
Optionally, when the obtained exception information further includes a target access parameter and a target error stack associated with the target exception error code, the policy determining module 320 is specifically further configured to determine a target error code configuration file including the target exception error code, the target access parameter, and the target error stack, where the target error code configuration file includes error code processing policies adopted for processing the target exception error code in different language environments.
Optionally, the policy determining module 320 is specifically further configured to search a target error code configuration file including a target abnormal error code, a target access parameter and a target error stack from the cache; and searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from the database based on the unsearched result.
Optionally, the policy determining module 320 is specifically further configured to search, based on the exception type of the target exception error code, a target error code configuration file including the target exception error code, the target access parameter and the target error stack from the first-level cache; the first-level cache is used for temporarily storing a plurality of first error code configuration files, wherein the plurality of first error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of non-business abnormal types under different language environments; searching a target error code configuration file comprising a target abnormal error code, a target access parameter and a target error stack from the second-level cache based on a result which is not searched in the first-level cache; the second-level cache is used for temporarily storing a plurality of second error code configuration files, wherein the plurality of second error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of abnormal business types under different language environments.
Optionally, the exception handling device provided by the invention may further include a log record module, configured to obtain call chain information corresponding to the service handling request; and determining error code log information based on the call chain information and the target error code processing strategy, and performing log record on the error code log information.
Optionally, the exception response module 310 is specifically configured to respond to an initial service processing request initiated by the client; and identifying the current language environment from the initial service processing request, and binding the identified current language environment with the initial service processing request to obtain the service processing request carrying the current language environment.
Optionally, the exception handling device provided by the invention may further include a document prompting module, configured to feed back an exception handling result to the client based on a feedback manner configured in advance in a visualized manner.
Fig. 4 illustrates a physical schematic diagram of an electronic device, as shown in fig. 4, which may include: processor 410, communication interface (Communications Interface) 420, memory 430 and communication bus 440, wherein processor 410, communication interface 420 and memory 430 communicate with each other via communication bus 440. The processor 410 may call logic instructions in the memory 430 to perform the following method:
Responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the anomaly information comprises a target anomaly error code; determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance in a visualized manner; and performing exception handling on the target exception error code by using a target error code handling strategy.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the related art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, embodiments of the present invention disclose a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, are capable of performing the methods provided by the above-described method embodiments, for example comprising:
responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the anomaly information comprises a target anomaly error code; determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance in a visualized manner; and performing exception handling on the target exception error code by using a target error code handling strategy.
In yet another aspect, embodiments of the present invention further provide a non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor is implemented to perform the transmission method provided in the above embodiments, for example, including:
responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the anomaly information comprises a target anomaly error code; determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from error code processing strategies adopted for processing different abnormal error codes in different language environments configured in advance in a visualized manner; and performing exception handling on the target exception error code by using a target error code handling strategy.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on such understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the related art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that the above-mentioned embodiments are merely illustrative of the invention, and not limiting. While the invention has been described in detail with reference to the embodiments, those skilled in the art will appreciate that various combinations, modifications, or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and it is intended to be covered by the scope of the claims of the present invention.
Claims (7)
1. An exception handling method, comprising:
responding to a service processing request carrying the current language environment, and acquiring abnormal information in the service processing process; the abnormal information comprises a target abnormal error code, a target access parameter and a target error stack, wherein the target access parameter is associated with the target abnormal error code, and the target access parameter comprises an input/output parameter corresponding to the occurrence of errors in the service processing process;
determining a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack, wherein the target error code configuration file comprises error code processing strategies adopted for processing the target abnormal error code under different language environments;
Determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from the target error code configuration file which is configured in a visualized manner in advance;
performing exception handling on the target exception error code by utilizing the target error code handling strategy;
wherein the determining includes the target abnormal error code, the target access parameter, and a target error code configuration file of the target error stack includes: searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a cache;
the searching the target error code configuration file including the target abnormal error code, the target access parameter and the target error stack from the cache comprises the following steps: searching a target error code configuration file comprising the target error code, the target access parameter and the target error stack from a first-level cache based on the abnormal type of the target error code; the first-level cache is used for temporarily storing a plurality of first error code configuration files, wherein the plurality of first error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of non-business abnormal types under different language environments; searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a second-level cache based on the result which is not searched in the first-level cache; the second-level cache is used for temporarily storing a plurality of second error code configuration files, wherein the plurality of second error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of abnormal business types in different language environments; the non-business abnormality types comprise space pointer abnormality, connection abnormality, SQL database abnormality and other abnormality caused by database downtime and network instability, and the business abnormality types comprise inventory shortage abnormality, record repetition abnormality and general business abnormality thrown out in the process of program operation caused by the fact that a developer considers the abnormality;
And searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a database based on the results which are not searched by the first-level cache and the second-level cache.
2. The exception handling method according to claim 1, wherein the method further comprises:
acquiring call chain information corresponding to the service processing request;
and determining error code log information based on the call chain information and the target error code processing strategy, and carrying out log record on the error code log information.
3. The exception handling method according to claim 1, wherein the determining process of the service handling request carrying the current language environment comprises:
responding to an initial service processing request initiated by a client;
and identifying the current language environment from the initial service processing request, and binding the identified current language environment with the initial service processing request to obtain the service processing request carrying the current language environment.
4. A method of exception handling according to any one of claims 1 to 3, further comprising:
And feeding back an exception processing result to the client based on a feedback mode of the pre-visualization configuration.
5. An abnormality processing apparatus, comprising:
the abnormal response module is used for responding to the service processing request carrying the current language environment and acquiring abnormal information in the service processing process; the abnormal information comprises a target abnormal error code, a target access parameter and a target error stack, wherein the target access parameter is associated with the target abnormal error code, and the target access parameter comprises an input/output parameter corresponding to the occurrence of errors in the service processing process;
the strategy determining module is used for determining a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack, wherein the target error code configuration file comprises error code processing strategies adopted for processing the target abnormal error code under different language environments; determining a target error code processing strategy adopted for processing the target abnormal error code in the current language environment from the target error code configuration file which is configured in a visualized manner in advance;
the exception handling module is used for performing exception handling on the target exception error code by utilizing the target error code handling strategy;
Wherein the determining includes the target abnormal error code, the target access parameter, and a target error code configuration file of the target error stack includes: searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a cache;
the searching the target error code configuration file including the target abnormal error code, the target access parameter and the target error stack from the cache comprises the following steps: searching a target error code configuration file comprising the target error code, the target access parameter and the target error stack from a first-level cache based on the abnormal type of the target error code; the first-level cache is used for temporarily storing a plurality of first error code configuration files, wherein the plurality of first error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of non-business abnormal types under different language environments; searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a second-level cache based on the result which is not searched in the first-level cache; the second-level cache is used for temporarily storing a plurality of second error code configuration files, wherein the plurality of second error code configuration files comprise error code processing strategies adopted for processing abnormal error codes of abnormal business types in different language environments; the non-business abnormality types comprise space pointer abnormality, connection abnormality, SQL database abnormality and other abnormality caused by database downtime and network instability, and the business abnormality types comprise inventory shortage abnormality, record repetition abnormality and general business abnormality thrown out in the process of program operation caused by the fact that a developer considers the abnormality;
And searching a target error code configuration file comprising the target abnormal error code, the target access parameter and the target error stack from a database based on the results which are not searched by the first-level cache and the second-level cache.
6. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the exception handling method of any one of claims 1 to 4 when the program is executed by the processor.
7. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the exception handling method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311348624.8A CN117112368B (en) | 2023-10-18 | 2023-10-18 | Abnormality processing method, abnormality processing device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311348624.8A CN117112368B (en) | 2023-10-18 | 2023-10-18 | Abnormality processing method, abnormality processing device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117112368A CN117112368A (en) | 2023-11-24 |
| CN117112368B true CN117112368B (en) | 2024-03-22 |
Family
ID=88795000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311348624.8A Active CN117112368B (en) | 2023-10-18 | 2023-10-18 | Abnormality processing method, abnormality processing device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117112368B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106484425A (en) * | 2016-10-19 | 2017-03-08 | 济南浪潮高新科技投资发展有限公司 | A kind of abnormality eliminating method of policy-based configuration |
| CN106603520A (en) * | 2016-12-08 | 2017-04-26 | 深圳Tcl数字技术有限公司 | Abnormal information interception method and apparatus thereof |
| CN109471802A (en) * | 2018-11-01 | 2019-03-15 | 郑州云海信息技术有限公司 | A kind of method and device of abnormality processing in Python webpage |
| CN111767143A (en) * | 2020-06-24 | 2020-10-13 | 中国工商银行股份有限公司 | Transaction data processing method, device, equipment and system |
| CN113938461A (en) * | 2020-07-10 | 2022-01-14 | 中国移动通信集团浙江有限公司 | Domain name cache resolution query method, device, equipment and storage medium |
| CN114187107A (en) * | 2021-12-08 | 2022-03-15 | 中国建设银行股份有限公司 | Multi-element error prompt information processing method and device |
| CN114780615A (en) * | 2022-04-29 | 2022-07-22 | 维沃移动通信有限公司 | Error code management method and device thereof |
| CN116010016A (en) * | 2023-03-27 | 2023-04-25 | 北京沐融信息科技股份有限公司 | Method, device, electronic equipment and medium for switching abnormal languages of service by system |
| CN116339784A (en) * | 2023-03-31 | 2023-06-27 | 重庆长安汽车股份有限公司 | Emergency method and device for failure in upgrading vehicle application, vehicle, equipment and medium |
-
2023
- 2023-10-18 CN CN202311348624.8A patent/CN117112368B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106484425A (en) * | 2016-10-19 | 2017-03-08 | 济南浪潮高新科技投资发展有限公司 | A kind of abnormality eliminating method of policy-based configuration |
| CN106603520A (en) * | 2016-12-08 | 2017-04-26 | 深圳Tcl数字技术有限公司 | Abnormal information interception method and apparatus thereof |
| CN109471802A (en) * | 2018-11-01 | 2019-03-15 | 郑州云海信息技术有限公司 | A kind of method and device of abnormality processing in Python webpage |
| CN111767143A (en) * | 2020-06-24 | 2020-10-13 | 中国工商银行股份有限公司 | Transaction data processing method, device, equipment and system |
| CN113938461A (en) * | 2020-07-10 | 2022-01-14 | 中国移动通信集团浙江有限公司 | Domain name cache resolution query method, device, equipment and storage medium |
| CN114187107A (en) * | 2021-12-08 | 2022-03-15 | 中国建设银行股份有限公司 | Multi-element error prompt information processing method and device |
| CN114780615A (en) * | 2022-04-29 | 2022-07-22 | 维沃移动通信有限公司 | Error code management method and device thereof |
| CN116010016A (en) * | 2023-03-27 | 2023-04-25 | 北京沐融信息科技股份有限公司 | Method, device, electronic equipment and medium for switching abnormal languages of service by system |
| CN116339784A (en) * | 2023-03-31 | 2023-06-27 | 重庆长安汽车股份有限公司 | Emergency method and device for failure in upgrading vehicle application, vehicle, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117112368A (en) | 2023-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7925607B2 (en) | Transaction data processing system | |
| US8074230B2 (en) | Method and system for dynamic context based contact service | |
| US20240048514A1 (en) | Method for electronic impersonation detection and remediation | |
| CN113220540B (en) | Service management method, device, computer equipment and storage medium | |
| US20230269273A1 (en) | Executing Real-Time Message Monitoring to Identify Potentially Malicious Messages and Generate Instream Alerts | |
| CN112613993A (en) | Transaction data processing method and device, computer equipment and storage medium | |
| CN113157315A (en) | Method, device, equipment and medium for identifying difference information of different versions of software | |
| CN114567495B (en) | Network attack analysis method and server applied to cloud computing | |
| CN110191097A (en) | Detection method, system, equipment and the storage medium of login page safety | |
| CN117112368B (en) | Abnormality processing method, abnormality processing device, electronic equipment and storage medium | |
| US20220284045A1 (en) | Matching machine generated data entries to pattern clusters | |
| CN115242434A (en) | Application program interface API identification method and device | |
| KR20180118869A (en) | Integration security anomaly symptom monitoring system | |
| CN111966515A (en) | Business abnormal data processing method and device, computer equipment and storage medium | |
| EP3556084B1 (en) | Application-sensitive strategy for server decommissioning | |
| CN113032647A (en) | Data analysis system | |
| US7827287B2 (en) | Interim execution context identifier | |
| US20240104481A1 (en) | Generating Transaction Recommendations Based on Monitoring and Analyzing Consumer Transactions | |
| CN117951742A (en) | Data processing method, apparatus, device, medium, and program product | |
| CN115202750A (en) | Interface service calling method, device, management platform and medium based on micro service | |
| CN116843169A (en) | Work order processing method, apparatus, device, storage medium, and program product | |
| CN114240377A (en) | Data processing method, system and related device | |
| CN117350689A (en) | Message notification method, device, computer equipment and storage medium | |
| CN114239016A (en) | Data security processing method, system and storage medium | |
| CN117874681A (en) | Detection method and device based on user overall behavior portraits, medium and equipment |
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 |