CN111367750A - Exception handling method, device and equipment - Google Patents
Exception handling method, device and equipment Download PDFInfo
- Publication number
- CN111367750A CN111367750A CN201811597460.1A CN201811597460A CN111367750A CN 111367750 A CN111367750 A CN 111367750A CN 201811597460 A CN201811597460 A CN 201811597460A CN 111367750 A CN111367750 A CN 111367750A
- Authority
- CN
- China
- Prior art keywords
- specified
- exception
- abnormal object
- address information
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Abstract
The application provides an exception handling method, an exception handling device and equipment thereof, wherein the method comprises the following steps: acquiring an abnormal object generated in the running process of a client; adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception; and outputting the modified abnormal object. According to the technical scheme, the abnormal problems can be repaired in time, the abnormal reasons are prevented from being analyzed manually by the user, the workload of the user is reduced, and the service experience is good.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to an exception handling method, apparatus, and device.
Background
The APM (Application Performance Management) is a solution for performing Performance Management and fault Management of an Application by monitoring the Application in real time. The APM can monitor and optimize the application program, thereby improving the reliability and quality of the application program, ensuring that a user obtains good service, reducing the total IT cost of ownership, and improving competitiveness.
In the process of monitoring the application program, once the application program is abnormal, an abnormal log is generated and used for recording abnormal information, and maintainers can analyze abnormal reasons through the abnormal log.
However, the workload of the maintainers for analyzing the abnormal reason is relatively large, the abnormal reason may not be accurately analyzed, and even if the abnormal reason is analyzed, the abnormal problem may not be repaired, so that the business experience is relatively poor.
Disclosure of Invention
The application provides an exception handling method, which comprises the following steps:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
The application provides an exception handling method, which comprises the following steps:
monitoring events executed by a client in the running process of the client;
when the client executes a specified event, acquiring an abnormal log corresponding to the specified event;
adding a specified URL address in the abnormal log to obtain a modified abnormal log; wherein the page corresponding to the specified URL address includes a processing policy for resolving an exception;
and outputting the modified exception log.
The present application provides an exception handling apparatus, the apparatus comprising:
the acquisition module is used for acquiring an abnormal object generated in the running process of the client;
the processing module is used for adding specified address information in the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and the output module is used for outputting the modified abnormal object.
The present application provides an exception handling apparatus, the apparatus comprising:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
Based on the above technical solution, in the embodiment of the present application, designated address information may be added to the abnormal object, the page corresponding to the designated address information may include a processing policy (such as an exception handling toolbox) for resolving the exception, and after the abnormal object is output to the user, the user may access the page corresponding to the designated address information and obtain the processing policy from the page. Therefore, the user can use the processing strategy to process the abnormity, namely the abnormity problem can be automatically solved based on the processing strategy, the abnormity problem can be timely repaired, the user is prevented from manually analyzing the abnormity reason, the workload of the user is reduced, and the service experience is good.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a flow diagram of an exception handling method in one embodiment of the present application;
FIG. 2 is a flow diagram of an exception handling method in another embodiment of the present application;
FIGS. 3A and 3B are schematic diagrams of an application scenario in an embodiment of the present application;
FIG. 4 is a flow diagram of an exception handling method in another embodiment of the present application;
fig. 5 is a block diagram of an abnormality processing apparatus according to an embodiment of the present application;
fig. 6 is a hardware configuration diagram of an exception handling apparatus according to an embodiment of the present application.
Detailed Description
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
An exception handling method provided in the embodiment of the present application may be applied to any device (e.g., a terminal device), and referring to fig. 1, as a schematic flow diagram of the method, the method may include:
Specifically, in the running process of the client, an event executed by the client can be monitored; when the client executes the specified event, the abnormal object corresponding to the specified event can be acquired.
The obtaining of the abnormal object corresponding to the specified event may include, but is not limited to: if the operation of executing the specified event by the client fails, the abnormal object corresponding to the specified event can be acquired. In one example, the exception object may be used to record operation information corresponding to a current operation.
In the above embodiments, the exception object may include, but is not limited to: and (6) exception logging.
102, adding specified address information in the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information includes a processing policy for resolving the exception.
Wherein, adding the specified address information in the abnormal object may include: adding specified address information to a first line of the exception object; alternatively, the specified address information is added to the last line of the exception object.
In one example, adding the specified address information to the first line of the exception object may include, but is not limited to: adding specified address information behind the first line of content of the exception object; or, adding the appointed address information in front of the first line content of the abnormal object. Adding specified address information to the last line of the exception object may include, but is not limited to: adding specified address information behind the last line of content of the exception object; or, adding the appointed address information in front of the last line of the abnormal object.
In the above embodiment, the specified address information may include, but is not limited to: a URL (uniform resource Locator) address is specified. Furthermore, the processing policy may include, but is not limited to: an exception handling toolbox, i.e. a toolbox for solving exception problems, such as software for solving exceptions.
In one example, the exception problem may be resolved by the exception handling tool box by outputting the modified exception object, i.e., outputting the exception object including the specified address information to the user to enable the user to access the page corresponding to the specified address information and downloading the exception handling tool box from the page.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. Moreover, in other embodiments, the steps of the respective methods do not have to be performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the above technical solution, in the embodiment of the present application, designated address information may be added to the abnormal object, the page corresponding to the designated address information may include a processing policy (such as an exception handling toolbox) for resolving the exception, and after the abnormal object is output to the user, the user may access the page corresponding to the designated address information and obtain the processing policy from the page. Therefore, the user can use the processing strategy to process the abnormity, namely the abnormity problem can be automatically solved based on the processing strategy, the abnormity problem can be timely repaired, the user is prevented from manually analyzing the abnormity reason, the workload of the user is reduced, and the service experience is good.
Based on the same application concept as the above method, another exception handling method is also proposed in the embodiment of the present application, and as shown in fig. 2, the method is a schematic flow diagram of the method, and may include:
In one example, adding a specified URL address to the exception log may include, but is not limited to: the specified URL address is added after the first line of content of the exception log.
And step 204, outputting the modified exception log.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. Moreover, in other embodiments, the steps of the respective methods do not have to be performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the above technical solution, in the embodiment of the application, a specified URL address may be added to the exception log, the page corresponding to the specified URL address may include a processing policy (such as an exception handling toolbox) for resolving the exception, and after the exception log is output to the user, the user may access the page corresponding to the specified URL address and obtain the processing policy from the page. Therefore, the user can use the processing strategy to process the abnormity, namely the abnormity problem can be automatically solved based on the processing strategy, the abnormity problem can be timely repaired, the user is prevented from manually analyzing the abnormity reason, the workload of the user is reduced, and the service experience is good.
The above technical solution is explained below with reference to specific application scenarios. Fig. 3A is a schematic view of an application scenario in the embodiment of the present application. The client may be a browser of a terminal device (such as an intelligent terminal, a notebook computer, a PC (personal computer), a mobile phone, and the like, without limitation), or may be an APP (application program) of the terminal device, without limitation. The server may be any device that interacts with the client and may provide relevant services for the client, which is not limited herein.
In this embodiment of the present application, a plug-in may be loaded at a client, where the plug-in is used to implement an exception handling method, and for convenience of description, the plug-in may be referred to as a proxy plug-in, or may be referred to as a target plug-in or an object plug-in, and the proxy plug-in is taken as an example in the following. Fig. 3B is a schematic diagram of the networking after the proxy plugin is installed. Of course, in practical application, other entities may also be used to implement the exception handling method, and the exception handling method is not limited to being implemented by using a proxy plug-in, for example, the client itself may implement the exception handling method, or other devices of the terminal device may implement the exception handling method, which is not limited to this.
Based on the application scenario, a flowchart of the exception handling method provided in the embodiment of the present application may refer to fig. 4, and the method may be applied to a terminal device, for example, the terminal device implements the exception handling method through a client, or the terminal device implements the exception handling method through a proxy plug-in, or the terminal device implements the exception handling method through another device, which is not limited to this, and the method may include:
Specifically, if the operation of executing the specified event by the client fails, an exception log corresponding to the specified event may be obtained, and the exception log may be used to record operation information corresponding to the current operation. If the operation of executing the specified event by the client is successful, the abnormal log corresponding to the specified event may not be acquired.
In one example, a proxy plugin can be loaded on a client, and the proxy plugin can monitor each event executed by the client and determine whether the event is a specified event. If the event is not the specified event, the agent plug-in no longer obtains the operation result of the event and continues to monitor the next event executed by the client. If the event is a specified event, the agent plug-in can also obtain the operation result of the specified event; if the operation result is that the operation is successful, the agent plug-in can not obtain the abnormal log corresponding to the specified event and continue to monitor the next event executed by the client; if the operation result is operation failure, the proxy plug-in can obtain the abnormal log corresponding to the specified event and continue to monitor the next event executed by the client.
When the client executes the specified event, if the operation result of the specified event is operation failure, the client may generate an exception log, and the proxy plug-in may obtain the exception log and process the exception log (that is, process the exception log of the client, and the processed exception log is still stored in the client), where the specific processing manner refers to the following steps. Or, when the client executes the specified event, if the operation result of the specified event is operation failure, the server may generate an exception log, and the proxy plug-in may obtain the exception log and process the exception log (that is, process the exception log of the server, and the processed exception log is still stored in the server), where the specific processing manner refers to the following steps.
The exception log may be a log in the process of calling the program, and is a log generated when the operation result of the specified event is an operation failure (i.e., the program has a problem), such as a log of about 100 lines.
For example, the specified event may be an operation of a database (e.g., writing data in the database, reading data from the database, etc.), and the agent plug-in may monitor each event executed by the client during the operation of the client by the user, for example, each event in a product ordering process, each event in a product searching process, each event in a shopping cart adding process, etc., without limitation. Taking each event in the commodity ordering process as an example, if the database needs to be operated when the event is executed, it can be shown that the event is a specified event; if the database does not need to be operated when the event is executed, it can be stated that the event is not a specified event.
And for each event in the commodity ordering process, if the event is not a specified event, the agent plug-in does not obtain the operation result of the event. If the event is a specified event, the proxy plugin can obtain the operation result of the specified event. For example, if the data is successfully written in the database, the operation result of the specified event is the operation success; or, if the data is successfully read from the database, the operation result of the specified event is successful; or, if the data writing in the database fails, the operation result of the specified event is operation failure; alternatively, if the data read from the database fails, the operation result of the specified event is an operation failure.
Further, if the operation result of the specified event is an operation failure, the server may further generate an exception log, and the proxy plugin may obtain the exception log, where the exception log is used to record operation information corresponding to the current operation, such as information about data failure written in the database, information about data failure read from the database, operation time information, exception cause information, and the like, and the content of the exception log is not limited.
And step 403, adding a specified URL address behind the first line of content of the exception log to obtain the modified exception log, wherein the page corresponding to the specified URL address comprises a processing strategy for solving the exception.
Of course, the specified URL address may also be added at other positions of the exception log, which is not limited in this regard. For example, a specified URL address may be added in front of the first line of content (e.g., in front of all content) of the exception log, resulting in a modified exception log; alternatively, a specified URL address may be added after the last line of the exception log (e.g., after all contents), resulting in a modified exception log; or, a specified URL address may be added in front of the last line of the exception log to obtain the modified exception log.
Since the exception log may include a plurality of lines of content, for example, 100 lines of content, in order to facilitate the user to view the specified URL address, the specified URL address may be added to the rearmost of the first line of content, so that the user may know the specified URL address from the rearmost of the first line of content by viewing the first line of content. Alternatively, the specified URL address may be added to the forefront of the first line of content, so that the user can know the specified URL address from the forefront of the first line of content by viewing the first line of content.
In one example, the specified URL address may be added to the exception log based on the bytecode-enhanced function, but in practical applications, the specified URL address may also be added to the exception log based on another function, which is not limited as long as the specified URL address can be added to the exception log.
In one example, the user accesses the page corresponding to the specified URL address by outputting the modified exception log, that is, outputting the exception log including the specified URL address to the user, that is, quickly accessing the page through the specified URL address. Since the page includes a handling policy for resolving the exception, such as an exception handling toolbox (i.e., a toolbox for resolving the exception, such as software for resolving the exception, etc.), the user may download the exception handling toolbox from the page and then resolve the exception via the exception handling toolbox.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. Moreover, in other embodiments, the steps of the respective methods do not have to be performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the above technical solution, in the embodiment of the present application, designated address information may be added to the abnormal object, the page corresponding to the designated address information may include a processing policy (such as an exception handling toolbox) for resolving the exception, and after the abnormal object is output to the user, the user may access the page corresponding to the designated address information and obtain the processing policy from the page. Therefore, the user can use the processing strategy to process the abnormity, namely the abnormity problem can be automatically solved based on the processing strategy, the abnormity problem can be timely repaired, the user is prevented from manually analyzing the abnormity reason, the workload of the user is reduced, and the service experience is good.
Based on the same application concept as the method, an embodiment of the present application further provides an exception handling apparatus, as shown in fig. 5, where the apparatus is a structural diagram of the exception handling apparatus, and the apparatus may include:
an obtaining module 51, configured to obtain an abnormal object generated in a client running process;
the processing module 52 is configured to add specified address information to the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
an output module 53, configured to output the modified exception object.
The obtaining module 51 is specifically configured to, when obtaining an abnormal object generated in the client running process:
monitoring events executed by a client in the running process of the client;
when the client executes a specified event, acquiring an abnormal object corresponding to the specified event;
the obtaining module 51 is specifically configured to, when obtaining the abnormal object corresponding to the specified event:
if the operation of executing the specified event by the client fails, acquiring an abnormal object corresponding to the specified event; the abnormal object is used for recording operation information corresponding to the current operation.
The processing module 52 is specifically configured to, when adding the specified address information to the abnormal object:
adding the specified address information to a first line of the abnormal object; alternatively, the first and second electrodes may be,
adding the specified address information to the last line of the abnormal object;
the processing module 52 is specifically configured to, when the specified address information is added to the first row of the abnormal object:
adding the specified address information behind the first line content of the exception object; alternatively, the first and second electrodes may be,
and adding the specified address information in front of the first line content of the exception object.
Based on the same application concept as the method, an embodiment of the present application further provides an exception handling apparatus, including: a processor and a machine-readable storage medium; wherein the machine-readable storage medium has stored thereon a plurality of computer instructions, and the processor executes the computer instructions to perform the following:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
An embodiment of the present application further provides a machine-readable storage medium, where a number of computer instructions are stored on the machine-readable storage medium, and when executed, the computer instructions perform the following processes:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
Referring to fig. 6, which is a structural diagram of an exception handling apparatus proposed in the embodiment of the present application, the exception handling apparatus 60 may include: a processor 61, a network interface 62, a bus 63, and a memory 64.
The memory 64 may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the memory 64 may be: RAM (random Access Memory), volatile Memory, non-volatile Memory, flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., a compact disk, a dvd, etc.).
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (13)
1. A method of exception handling, the method comprising:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
2. The method of claim 1,
the acquiring of the abnormal object generated in the client operation process includes:
monitoring events executed by a client in the running process of the client;
and when the client executes the specified event, acquiring the abnormal object corresponding to the specified event.
3. The method of claim 2,
the acquiring of the abnormal object corresponding to the specified event includes:
if the operation of executing the specified event by the client fails, acquiring an abnormal object corresponding to the specified event; the abnormal object is used for recording operation information corresponding to the current operation.
4. The method of claim 1,
adding specified address information to the abnormal object specifically comprises:
adding the specified address information to a first line of the abnormal object; alternatively, the first and second electrodes may be,
and adding the specified address information to the last line of the abnormal object.
5. The method of claim 4,
adding specified address information to the first line of the abnormal object specifically comprises:
adding the specified address information behind the first line content of the exception object; alternatively, the first and second electrodes may be,
and adding the specified address information in front of the first line content of the exception object.
6. The method of claim 1,
the processing strategy comprises an exception handling tool kit, and the method further comprises:
and outputting the modified exception object to enable a user to access a page corresponding to the specified address information, and downloading the exception handling toolbox from the page.
7. The method of any one of claims 1-6, wherein the abnormal object comprises: an exception log; the specified address information includes: a uniform resource locator, URL, address is specified.
8. A method of exception handling, the method comprising:
monitoring events executed by a client in the running process of the client;
when the client executes a specified event, acquiring an abnormal log corresponding to the specified event;
adding a specified URL address in the abnormal log to obtain a modified abnormal log; wherein the page corresponding to the specified URL address includes a processing policy for resolving an exception;
and outputting the modified exception log.
9. The method of claim 8,
adding a specified URL address in the abnormal log specifically comprises:
adding the specified URL address behind the first line of content of the exception log.
10. An exception handling apparatus, the apparatus comprising:
the acquisition module is used for acquiring an abnormal object generated in the running process of the client;
the processing module is used for adding specified address information in the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and the output module is used for outputting the modified abnormal object.
11. The apparatus of claim 10,
the obtaining module is specifically configured to, when obtaining an abnormal object generated in the client running process:
monitoring events executed by a client in the running process of the client;
when the client executes a specified event, acquiring an abnormal object corresponding to the specified event;
the obtaining module is specifically configured to, when obtaining the abnormal object corresponding to the specified event:
if the operation of executing the specified event by the client fails, acquiring an abnormal object corresponding to the specified event; the abnormal object is used for recording operation information corresponding to the current operation.
12. The apparatus of claim 10,
the processing module is specifically configured to, when adding the specified address information to the abnormal object:
adding the specified address information to a first line of the abnormal object; alternatively, the first and second electrodes may be,
adding the specified address information to the last line of the abnormal object;
the processing module is specifically configured to, when adding the specified address information to the first row of the abnormal object:
adding the specified address information behind the first line content of the exception object; alternatively, the first and second electrodes may be,
and adding the specified address information in front of the first line content of the exception object.
13. An exception handling apparatus, characterized in that the apparatus comprises:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
acquiring an abnormal object generated in the running process of a client;
adding specified address information into the abnormal object to obtain a modified abnormal object; wherein the page corresponding to the specified address information comprises a processing strategy for solving an exception;
and outputting the modified abnormal object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811597460.1A CN111367750B (en) | 2018-12-26 | 2018-12-26 | Exception handling method, device and equipment thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811597460.1A CN111367750B (en) | 2018-12-26 | 2018-12-26 | Exception handling method, device and equipment thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111367750A true CN111367750A (en) | 2020-07-03 |
| CN111367750B CN111367750B (en) | 2023-06-20 |
Family
ID=71209878
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811597460.1A Active CN111367750B (en) | 2018-12-26 | 2018-12-26 | Exception handling method, device and equipment thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111367750B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115672756A (en) * | 2022-11-15 | 2023-02-03 | 艾信智慧医疗科技发展（苏州）有限公司 | Abnormal condition processing method for medical box type logistics sorting system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102681931A (en) * | 2012-05-15 | 2012-09-19 | 天津市天元新泰科技发展有限公司 | Realization method of log and abnormal probe |
| CN105120485A (en) * | 2015-09-11 | 2015-12-02 | 中国联合网络通信集团有限公司 | Positioning method and positioning system for abnormal events |
| CN106598811A (en) * | 2016-12-19 | 2017-04-26 | 深圳天珑无线科技有限公司 | Abnormal event processing method and apparatus, and terminal |
| US20170139806A1 (en) * | 2015-11-18 | 2017-05-18 | Nec Laboratories America, Inc. | Automated Anomaly Detection Service on Heterogeneous Log Streams |
| CN107423090A (en) * | 2017-06-29 | 2017-12-01 | 武汉斗鱼网络科技有限公司 | A kind of Flash player abnormal log management method and system |
| US20190332513A1 (en) * | 2017-04-26 | 2019-10-31 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for dealing with abnormality of application program and storage medium |
-
2018
- 2018-12-26 CN CN201811597460.1A patent/CN111367750B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102681931A (en) * | 2012-05-15 | 2012-09-19 | 天津市天元新泰科技发展有限公司 | Realization method of log and abnormal probe |
| CN105120485A (en) * | 2015-09-11 | 2015-12-02 | 中国联合网络通信集团有限公司 | Positioning method and positioning system for abnormal events |
| US20170139806A1 (en) * | 2015-11-18 | 2017-05-18 | Nec Laboratories America, Inc. | Automated Anomaly Detection Service on Heterogeneous Log Streams |
| CN106598811A (en) * | 2016-12-19 | 2017-04-26 | 深圳天珑无线科技有限公司 | Abnormal event processing method and apparatus, and terminal |
| US20190332513A1 (en) * | 2017-04-26 | 2019-10-31 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for dealing with abnormality of application program and storage medium |
| CN107423090A (en) * | 2017-06-29 | 2017-12-01 | 武汉斗鱼网络科技有限公司 | A kind of Flash player abnormal log management method and system |
Non-Patent Citations (1)
| Title |
|---|
| 朱剑锋;缪万胜;康介祥;: "基于堆栈回溯的异常处理" * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115672756A (en) * | 2022-11-15 | 2023-02-03 | 艾信智慧医疗科技发展（苏州）有限公司 | Abnormal condition processing method for medical box type logistics sorting system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111367750B (en) | 2023-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102387169B (en) | Delete method, system and delete server for distributed cache objects | |
| CN111414389B (en) | Data processing method and device, electronic equipment and storage medium | |
| US10078579B1 (en) | Metrics-based analysis for testing a service | |
| CN105183669A (en) | Data storage method and device | |
| CN103152391A (en) | Journal output method and device | |
| US9026612B2 (en) | Generating a custom parameter rule based on a comparison of a run-time value to a request URL | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN111597093B (en) | Exception handling method, device and equipment thereof | |
| CN116644250B (en) | Page detection method, page detection device, computer equipment and storage medium | |
| CN111367750B (en) | Exception handling method, device and equipment thereof | |
| CN110502486B (en) | Log processing method and device, electronic equipment and computer readable storage medium | |
| US7721156B2 (en) | Selective logging of computer activity | |
| US20160371486A1 (en) | Capturing correlations between activity and non-activity attributes using n-grams | |
| CN110928941A (en) | Data fragment extraction method and device | |
| CN112818204B (en) | Service processing method, device, equipment and storage medium | |
| CN113111078B (en) | Resource data processing method and device, computer equipment and storage medium | |
| JP2017068691A (en) | Diagnostic program, diagnostic method and diagnostic apparatus | |
| CN111262727B (en) | Service capacity expansion method, device, equipment and storage medium | |
| CN105988917B (en) | Abnormal information acquisition method and device | |
| CN110266610B (en) | Traffic identification method and device and electronic equipment | |
| CN108268662B (en) | Social graph generation method based on H5 page, electronic device and storage medium | |
| CN110019262B (en) | Data updating method and device | |
| US10187251B1 (en) | Event processing architecture for real-time member engagement | |
| CN111225075A (en) | Configuration method and device for Internet of things directional access service | |
| CN111444057A (en) | Page performance data acquisition method and device and computing 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 |