CN113760643A

CN113760643A - Application program exception handling method and device, electronic equipment and storage medium

Info

Publication number: CN113760643A
Application number: CN202110201684.1A
Authority: CN
Inventors: 艾佳; 王宇森
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2021-02-23
Filing date: 2021-02-23
Publication date: 2021-12-07

Abstract

An embodiment of the application provides an exception handling method, an exception handling device, an electronic device, a storage medium and a program product, which include: monitoring an application program accessing a webpage, wherein the application program is generated based on Structured Query Language (SQL), if the abnormal SQL which cannot be identified of the application program is monitored, determining abnormal information corresponding to the abnormal SQL according to a preset column database, wherein the column database is a database for storing SQL, generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL, and the prompt information is used for prompting the reason why the webpage cannot be normally accessed through the application program.

Description

Application program exception handling method and device, electronic equipment and storage medium

Technical Field

The embodiment of the application relates to the technical field of computers and the technical field of internet, in particular to an exception handling method and device of an application program, electronic equipment, a storage medium and a program product.

Background

An Application Programming Interface (API), which may also be referred to as an Application Programming Interface, is a predefined Interface (e.g., a function, an HTTP Interface, a JSF Interface, etc.), or a convention for linking different components of a software system.

In the API test or application process, an abnormal condition may occur in the running process of the application program of the API, such as an illegal input of a user in the application program, or a file path in the application program may not find a corresponding file, and so on. In the prior art, an exception handling method is generally adopted, which includes: and identifying and processing the exception of the application program by adopting a Spring exception handling framework.

However, the Spring exception handling framework cannot handle the unrecognized abnormal Structured Query Language (SQL), that is, the existing method in the prior art has an unrecognized abnormal SQL, so that the exception handling needs to be performed in a manual manner, which may cause a problem of low reliability of exception handling.

Disclosure of Invention

The embodiment of the application provides an exception handling method and device for an application program, electronic equipment, a storage medium and a program product, which are used for solving the problem that the reliability of exception handling is low.

In a first aspect, an embodiment of the present application provides an exception handling method for an application program, including:

monitoring an application program accessing a webpage, wherein the application program is generated based on a Structured Query Language (SQL);

if the abnormal SQL which cannot be identified of the application program is monitored, determining abnormal information corresponding to the abnormal SQL according to a preset column database, wherein the column database is a database for storing the SQL;

and generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL, wherein the prompt information is used for prompting the reason why the webpage cannot be normally accessed through the application program.

In some embodiments, if the application program is an application program of a first application program interface, generating and outputting a prompt message according to the exception information corresponding to the exception SQL, including:

determining that the abnormal information corresponding to the abnormal SQL corresponds to the abnormal information of the second application program interface according to a preset mapping relation between the abnormal information of the first application program interface and the abnormal information of the second application program interface;

and generating and outputting prompt information according to the abnormal information of the second application program interface.

In some embodiments, generating and outputting a prompt message according to the exception information of the second application program interface includes:

determining an error code corresponding to the abnormal information of the second application program interface according to a preset mapping relation between the abnormal information and the error code;

and generating and outputting the prompt information according to the error code corresponding to the abnormal information of the second application program interface.

In some embodiments, generating and outputting the prompt information according to the error code corresponding to the exception information of the second application program interface includes:

determining an exception type corresponding to an error code corresponding to exception information of the second application program interface according to a preset mapping relation between the error code and the exception type, wherein the exception type comprises: the method comprises the following steps that the application program cannot normally access a webpage due to user operation, and the application program cannot normally access the webpage due to the application program;

if the abnormal type is an abnormality that the application program cannot normally access the webpage due to user operation, generating and outputting information for prompting that the abnormality is an abnormality that the application program cannot normally access the webpage due to user operation;

and if the exception type is the exception that the webpage cannot be normally accessed, which is caused by the application program, generating and outputting information for prompting the exception that the webpage cannot be normally accessed, which is caused by the application program.

In some embodiments, after determining an error code corresponding to the exception information of the second application program interface according to a preset mapping relationship between the exception information and the error code, the method further includes:

determining an alarm level corresponding to an error code corresponding to the abnormal information of the second application program interface according to a mapping relation between a preset error code and the alarm level;

and generating log information based on the abnormal information of the second application program interface and the determined alarm level.

In some embodiments, determining the exception information corresponding to the exception SQL according to a preset column database includes:

if the column-type database is abnormal, determining abnormal information corresponding to the abnormal SQL according to the abnormal column-type database;

and if the column database is normal, determining the attribute information of the abnormal SQL as the abnormal information corresponding to the abnormal SQL.

In some embodiments, determining exception information corresponding to the exception SQL from an exception columnar database comprises:

acquiring abnormal content of the abnormal columnar database, and determining an abnormal code of the abnormal SQL according to the abnormal content;

determining an abnormal type corresponding to the abnormal code of the abnormal SQL according to a mapping relation between a preset abnormal code and the abnormal type;

and instantiating the abnormal type corresponding to the abnormal code of the abnormal SQL to obtain the abnormal information corresponding to the abnormal SQL.

In some embodiments, after determining the exception information corresponding to the exception SQL according to a preset columnar database, the method further comprises:

and if the abnormal information corresponding to the abnormal SQL is lost, acquiring the abnormal information in a preset abnormal stack, and generating and outputting prompt information according to the abnormal information in the preset abnormal stack.

In a second aspect, an embodiment of the present application provides an exception handling apparatus for an application program, including:

the monitoring unit is used for monitoring an application program accessing a webpage, wherein the application program is generated based on a Structured Query Language (SQL);

the determining unit is used for determining abnormal information corresponding to the abnormal SQL according to a preset column database if the abnormal SQL of the application program is monitored, wherein the column database is a database for storing the SQL;

the generating unit is used for generating prompt information according to the abnormal information corresponding to the abnormal SQL, wherein the prompt information is used for prompting the reason why the webpage cannot be normally accessed through the application program;

and the output unit is used for outputting the prompt information.

In some embodiments, if the application is an application of a first application program interface, the generating unit includes:

the first determining subunit is configured to determine, according to a preset mapping relationship between the abnormal information of the first application program interface and the abnormal information of the second application program interface, that the abnormal information corresponding to the abnormal SQL corresponds to the abnormal information of the second application program interface;

and the first generation subunit is used for generating prompt information according to the abnormal information of the second application program interface.

In some embodiments, the first generating subunit comprises:

the determining module is used for determining an error code corresponding to the abnormal information of the second application program interface according to a mapping relation between preset abnormal information and the error code;

and the generating module is used for generating the prompt information according to the error code corresponding to the abnormal information of the second application program interface.

In some embodiments, the generating module comprises:

the determining submodule is configured to determine, according to a preset mapping relationship between an error code and an exception type, an exception type corresponding to the error code corresponding to the exception information of the second application program interface, where the exception type includes: the method comprises the following steps that the application program cannot normally access a webpage due to user operation, and the application program cannot normally access the webpage due to the application program;

the generation submodule is used for generating and outputting information for prompting that the abnormality is the abnormality that the application program cannot normally access the webpage caused by the user operation if the abnormality type is the abnormality that the application program cannot normally access the webpage caused by the user operation;

the generation submodule is used for generating and outputting information for prompting the abnormality of the webpage which cannot be normally accessed and is caused by the application program if the abnormality type is the abnormality of the webpage which cannot be normally accessed and is caused by the application program.

In some embodiments, the generating unit comprises:

the second determining subunit is configured to determine, according to a mapping relationship between preset error codes and alarm levels, an alarm level corresponding to an error code corresponding to the abnormal information of the second application program interface;

and the second generation subunit is used for generating log information based on the abnormal information of the second application program interface and the determined alarm level.

In some embodiments, the determining unit is configured to determine, if the columnar database is abnormal, abnormal information corresponding to the abnormal SQL according to the abnormal columnar database, and if the columnar database is normal, determine the attribute information of the abnormal SQL as the abnormal information corresponding to the abnormal SQL.

In some embodiments, the determining unit comprises:

an acquiring subunit, configured to acquire abnormal content of the abnormal columnar database;

the third determining subunit is used for determining an abnormal code of the abnormal SQL according to the abnormal content;

the fourth determining subunit is configured to determine, according to a mapping relationship between a preset exception code and an exception type, an exception type corresponding to the exception code of the exception SQL;

and the processing subunit is used for performing instantiation processing on the abnormal type corresponding to the abnormal code of the abnormal SQL to obtain the abnormal information corresponding to the abnormal SQL.

In some embodiments, the apparatus further comprises:

and the obtaining unit is used for obtaining the abnormal information in a preset abnormal stack if the abnormal information corresponding to the abnormal SQL is lost, and generating and outputting prompt information according to the abnormal information in the preset abnormal stack.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

a memory; a memory for storing the processor-executable instructions;

wherein the processor is configured to perform the method of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, are configured to implement the method according to the first aspect.

In a fifth aspect, the present application provides a computer program product, which includes a computer program that, when executed by a processor, implements the method of the first aspect.

An embodiment of the application provides an exception handling method and device for an application program, an electronic device, a storage medium and a program product, and the exception handling method comprises the following steps: monitoring an application program accessing a webpage, wherein the application program is generated based on Structured Query Language (SQL), and if the application program is monitored to be unidentifiable abnormal SQL, determining abnormal information corresponding to the abnormal SQL according to a preset column database, wherein the column database is a database for storing SQL, and generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL, wherein the prompt information is used for prompting the reason why the webpage cannot be normally accessed by the application program, in the embodiment, when the abnormal SQL which cannot be identified by the application program is monitored by an abnormal processing device, determining the abnormal information of the unidentifiable abnormal SQL according to the column database, and the column database is the database for storing SQL, so that the determined abnormal information has higher accuracy and reliability, when the prompt information is generated and output based on the determined abnormal information, the technical effects of accuracy and reliability of the prompt information can be improved, and the reliability of the test can be met in a test scene, and the reliability of the application and the experience of the user can also be met in the application scene.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

Fig. 1 is a scene diagram of an exception handling method of an application program to which the embodiment of the present application is applicable;

FIG. 2 is a flowchart illustrating a method for exception handling for an application according to one embodiment of the present application;

FIG. 3 is a flowchart illustrating an exception handling method for an application according to another embodiment of the present application;

FIG. 4 is a flowchart illustrating an exception handling method for an application according to another embodiment of the present application;

FIG. 5 is a schematic diagram of an exception handling apparatus for an application according to one embodiment of the present application;

FIG. 6 is a diagram illustrating an exception handling apparatus for an application according to another embodiment of the present application;

fig. 7 is a schematic diagram of an electronic device according to an embodiment of the application.

With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

The terms referred to in the embodiments of the present application are explained as follows:

web page: the method refers to basic elements forming a website, and is a platform for bearing various website applications. A web page is a plain text file containing HTML tags, which can be stored in any computer, is a "page" of the world wide web, is in hypertext markup language format (an application of standard universal markup language, file extension. HTML or. htm), is usually provided with a picture file, and is readable by a web browser.

The application program comprises the following steps: refers to a computer program that operates in a user mode and that interacts with a user in order to perform one or more specific tasks.

Structured query language, SQL: is a special purpose programming language, a database query and programming language, used to access data and query, update and manage relational database systems. Structured query languages, by contrast, are high-level, non-procedural programming languages that allow users to work on high-level data structures. The method does not require a user to specify a data storage method and does not require the user to know a specific data storage mode, so that different database systems with completely different underlying structures can use the same structured query language as an interface for data input and management.

A column-wise database: the database is a database for storing data by a column-related storage architecture, and is mainly suitable for batch data processing and instant query. Correspondingly, the data is a line type database, and the data is subjected to space allocation by a line-related storage architecture, so that the method is mainly suitable for large-batch data processing and is commonly used for online transaction type data processing.

With the development of internet technology and terminal equipment technology, the API technology has a new breakthrough, and how to improve the reliability of API application becomes a focus of technical attention.

Generally speaking, in an API test or application process, there may be an abnormal situation that an application program of the API is abnormal in an operation process, which may cause an abnormal situation that a web page cannot be normally displayed when the application program accesses a certain web page.

That is to say, the exception handling method for the application program in the embodiment of the present application may be applied to a scenario of API test, and may also be applied to a scenario of API application.

Now, taking a scenario as an API test scenario as an example, a scenario to which the exception handling method of the application program according to the embodiment of the present application may be applied is exemplarily described.

Referring to fig. 1, fig. 1 is a scene diagram of an exception handling method for an application program, which can be applied to the embodiment of the present application.

As shown in fig. 1, the test device 101 is provided with an API, where an application program is stored, the application program is generated based on SQL, that is, the application program is written based on SQL, and the application program is used to access a web page.

A user 102 (e.g., a tester) may initiate a request to access a web page to the server 103 through the test device 101.

For example, as shown in FIG. 1, in some embodiments, the test device 101 may include a display of touch screen functionality upon which the user 102 may enter information related to a web page and trigger the test device 101 to send a request to access the web page to the server 103 by clicking a virtual button "search" as shown in FIG. 1.

In other embodiments, the test device 101 may include a sound collector, and the user 102 may trigger the test device 101 to send a request to the server 103 for access to a web page by voice.

Accordingly, the server 103 feeds back the web page to the test device 101 based on the request to access the web page.

Accordingly, the test device 101 receives the web page fed back by the server 103 and may output the web page through the display, i.e., display the web page through the display.

It should be noted that there may be a webpage error due to the operation of the user 102 or due to the application program itself, that is, the testing device 101 cannot normally output the webpage, and in order to avoid the above situation as much as possible, it is important to handle the exception of the application program.

In the related art, a Spring exception handling framework is usually adopted to handle exception SQL. The abnormal SQL may include unrecognized abnormal SQL, that is, unrecognized abnormal SQL, and when the abnormal SQL is unrecognized abnormal SQL, the Spring abnormal processing framework cannot process the unrecognized abnormal SQL, and although the abnormal processing may be performed by combining with a manual method, due to the influence of human subjective factors, there may be a problem that the reliability of the abnormal processing is low, and there may be a problem that the efficiency of the abnormal processing is low.

It should be noted that the above example is only used for exemplary illustration, and the exception handling method for the application program provided in this embodiment may be applied to a test scenario, and when the exception handling method for the application program provided in this application is applied to the application scenario, an implementation principle of the exception handling method is the same as that of the test scenario, and details are not described here again.

In order to solve the above problems, the inventors of the present application have made creative efforts to obtain the inventive concept of the present application: and determining abnormal information corresponding to the abnormal SQL which cannot be identified according to the column database, and generating and outputting prompt information based on the determined abnormal information.

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

Based on the inventive concept, the embodiment of the application provides an exception handling method for an application program.

Referring to fig. 2, fig. 2 is a flowchart illustrating an exception handling method for an application according to an embodiment of the present application.

As shown in fig. 2, the method includes:

s201: applications that are accessing web pages are monitored.

Wherein the application is generated based on the structured query language SQL.

For example, the execution main body of this embodiment may be an exception handling device (hereinafter, referred to as an exception handling device) of an application program, where the exception handling device may be a server (such as a local server or a cloud server), or may be a terminal device, or may be a processor, or may be a chip, and this embodiment is not limited.

For example, if the exception handling method of the application program of the present embodiment is applied to the application scenario shown in fig. 1, the exception handling apparatus may be the test equipment shown in fig. 1.

For another example, based on the above analysis, it can be known that the exception handling method of the application program according to this embodiment may also be applied to an application scenario, and if the exception handling method of the application program according to this embodiment is applied to the application scenario, the exception handling apparatus may be a terminal device in the application scenario, such as a user equipment (e.g., a mobile phone, a desktop computer, a notebook computer, a handheld device, and the like).

This step can be understood as: the exception handling means may monitor the application which is accessing the web page if the terminal device is accessing the web page through the application.

S202: if the abnormal SQL which cannot be identified by the application program is monitored, determining abnormal information corresponding to the abnormal SQL according to a preset column database.

The columnar database is a database for storing SQL.

It should be noted that when the processing device monitors the application program accessing the web page, there may be two monitoring results, one monitoring result is that the processing device monitors the identified abnormal SQL, and for the identified abnormal SQL, the method in the related art may be adopted to continue to execute the abnormal processing of the application program, for example, the method based on the Spring abnormal processing framework in the above example continues to execute the abnormal processing of the application program, and the specific implementation principle may be described with reference to the related art, and is not described herein again.

Another monitoring result is abnormal SQL which cannot be identified, and for the abnormal SQL which cannot be identified, the Spring exception handling framework cannot handle processing, so for this case, the present embodiment introduces a feature of determining exception information corresponding to the abnormal SQL which cannot be identified according to a preset column database, so as to continue to execute exception handling on the application program through the feature.

S203: and generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL.

The prompt information is used for prompting the reason why the webpage cannot be normally accessed through the application program.

Based on the above analysis, an embodiment of the present application provides an exception handling method for an application program, including: monitoring an application program accessing a webpage, wherein the application program is generated based on Structured Query Language (SQL), and if the application program is monitored to be unidentifiable abnormal SQL, determining abnormal information corresponding to the abnormal SQL according to a preset column database, wherein the column database is a database for storing SQL, and generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL, wherein the prompt information is used for prompting the reason why the webpage cannot be normally accessed by the application program, in the embodiment, when the abnormal SQL which cannot be identified by the application program is monitored by an abnormal processing device, determining the abnormal information of the unidentifiable abnormal SQL according to the column database, and the column database is the database for storing SQL, so that the determined abnormal information has higher accuracy and reliability, when the prompt information is generated and output based on the determined abnormal information, the technical effects of accuracy and reliability of the prompt information can be improved, and the reliability of the test can be met in a test scene, and the reliability of the application and the experience of the user can also be met in the application scene.

Referring to fig. 3, fig. 3 is a flowchart illustrating an exception handling method for an application according to another embodiment of the present application.

As shown in fig. 3, the method includes:

s301: applications that are accessing web pages are monitored.

For example, the description about S301 may refer to S201, which is not described herein again.

S302: it is determined whether the unrecognizable abnormal SQL of the application program is monitored, if so, S303 is executed, and if not, an abnormality processing method (not shown) of the application program in the related art is executed.

S303: and judging whether the column database is abnormal, if so, executing S304, and otherwise, executing S305.

S304: and determining abnormal information corresponding to the abnormal SQL according to the abnormal columnar database.

In some embodiments, S304 may include the steps of:

step 1: and acquiring abnormal content of the abnormal columnar database, and determining an abnormal code of the abnormal SQL according to the abnormal content.

The abnormal content can be understood as related content causing the column database to be abnormal, and different content causing the column database to be abnormal has different corresponding abnormal codes.

In some embodiments, a mapping relationship between the abnormal content and the abnormal code may be preset, and when the abnormality processing device acquires the content (i.e., the abnormal content) causing the abnormality of the columnar database, the abnormality processing device may determine, based on the mapping relationship between the abnormal content and the abnormal code, the abnormal code corresponding to the content causing the abnormality of the columnar database, where the determined abnormal code is the abnormal code of the abnormal SQL.

Step 2: and determining the abnormal type corresponding to the abnormal code of the abnormal SQL according to the preset mapping relation between the abnormal code and the abnormal type.

Illustratively, the exception types include: the application program is abnormal in that the application program cannot normally access the webpage due to user operation, and the application program itself is abnormal in that the webpage cannot normally access the webpage.

The embodiment can be understood as follows: the exception handling device may set a mapping relationship between the exception code and the exception type in advance, and when the exception handling device determines the exception code corresponding to the exception SQL, the exception type corresponding to the exception code of the exception SQL may be determined based on the mapping relationship between the exception code and the exception type.

And step 3: and instantiating the abnormal type corresponding to the abnormal code of the abnormal SQL to obtain the abnormal information corresponding to the abnormal SQL.

The instantiation processing can be understood as assigning processing to the exception type corresponding to the exception code of the exception SQL, so as to obtain the exception information corresponding to the exception SQL.

Similarly, the exception handling device may also pre-establish a mapping relationship between the assignment and the exception type, and when the exception handling device determines the exception type corresponding to the exception code of the exception SQL, the exception handling device may determine, based on the mapping relationship between the assignment and the exception type, the assignment of the exception type corresponding to the exception code of the exception SQL, to obtain the exception information corresponding to the exception SQL.

It should be noted that, in this embodiment, the anomaly code is determined based on the anomaly content, the anomaly type is determined based on the anomaly code, and the anomaly information is determined based on the anomaly type, so that the determined anomaly information is highly associated and attached to the anomaly content, and therefore, the technical effects of accuracy and reliability of the determined anomaly information can be achieved.

S305: and determining the attribute information of the abnormal SQL as the abnormal information corresponding to the abnormal SQL.

By way of example, this step may be understood as: if the abnormal processing device determines that the columnar database is normal, the abnormal processing device may acquire the attribute information of the abnormal SQL and determine the acquired attribute information as the abnormal information corresponding to the abnormal SQL.

The attribute information can be understood as related information such as SQL content of abnormal SQL.

It should be noted that, in this embodiment, by determining the abnormal information corresponding to the abnormal SQL from two dimensions, namely the abnormal dimension and the normal dimension, of the column-type database, the diversity and flexibility of determining the abnormal information corresponding to the abnormal SQL can be improved, and the technical effects of accuracy and reliability of the determined abnormal information corresponding to the abnormal SQL can be achieved.

S306: and generating and outputting prompt information according to the abnormal information corresponding to the abnormal SQL.

Illustratively, in conjunction with the scenario shown in FIG. 1, the exception handling apparatus may output a prompt based on the display when determining the prompt.

Referring to fig. 4, fig. 4 is a flowchart illustrating an exception handling method for an application according to another embodiment of the present application.

As shown in fig. 4, the method includes:

s401: applications that are accessing web pages are monitored.

For example, the description about S401 may refer to S201, which is not described herein again.

S402: if the abnormal SQL which cannot be identified by the application program is monitored, determining abnormal information corresponding to the abnormal SQL according to a preset column database.

The columnar database is a database for storing SQL.

For example, the description about S402 may refer to the description about S202, and may also refer to the descriptions about S302 to S305, which are not described herein again.

S403: if the application program is the application program of the first application program interface, determining that the abnormal information corresponding to the abnormal SQL corresponds to the abnormal information of the second application program interface according to a preset mapping relation between the abnormal information of the first application program interface and the abnormal information of the second application program interface.

Illustratively, the first application interface may be a Jeff (JSF) application interface and the second application interface may be an HTTP application interface.

Accordingly, this step can be understood as: if the application program is the application program of the JSF application program interface, the abnormal information of the HTTP application program interface corresponding to the abnormal information corresponding to the abnormal SQL may be determined based on the mapping relationship between the abnormal information of the JSF application program interface and the abnormal information of the HTTP application program interface.

It should be noted that, in this embodiment, through mapping of the exception information between two different application program interfaces (such as the JSF application program interface and the HTTP application program interface in this embodiment), a technical effect that the exception handling method of the application program of this embodiment is commonly used by different application program interfaces can be achieved, that is, a technical effect that the exception handling method of the application program of this embodiment is universal and flexible can be achieved.

S404: and generating and outputting prompt information according to the abnormal information of the second application program interface.

In some embodiments, S404 may include the steps of:

step 1: and determining an error code corresponding to the abnormal information of the second application program interface according to a preset mapping relation between the abnormal information and the error code.

Illustratively, with reference to the above example, if the second application program interface is an HTTP application program interface, the present embodiment may be understood as: the abnormality processing means may set a mapping relationship between the abnormality information and the error code in advance, and when the abnormality processing means determines the abnormality information of the HTTP application program interface, the error code corresponding to the abnormality information of the HTTP application program interface may be determined based on the mapping relationship.

Step 2: and generating and outputting prompt information according to the error code corresponding to the abnormal information of the second application program interface.

In some embodiments, step 2 may include the following sub-steps:

substep 1: and determining the abnormal type corresponding to the error code corresponding to the abnormal information of the second application program interface according to the preset mapping relation between the error code and the abnormal type.

Wherein the exception types include: the application program is abnormal in that the application program cannot normally access the webpage due to user operation, and the application program itself is abnormal in that the webpage cannot normally access the webpage.

The error codes may include two different types of error codes, one is a four-start error code, and the other is a five-start error code.

In this embodiment, the error code of the four heads may be defined as an error code that the application program cannot normally access the web page due to the user operation, that is, the exception type corresponding to the error code of the four heads may be that the application program cannot normally access the web page due to the user operation; accordingly, the fifths error code may be defined as an error code that the application itself cannot normally access the web page, i.e., the exception type corresponding to the fifths error code may be the type of the web page that the application itself cannot normally access.

Substep 2: and if the exception type is an exception that the application program cannot normally access the webpage due to the user operation, generating and outputting information for prompting the exception that the application program cannot normally access the webpage due to the exception being the user operation.

With reference to the above example, if the error code corresponding to the exception information of the HTTP application program interface is a four-headed error code, the exception handling apparatus generates and outputs information for prompting that the exception is an exception that the application program cannot normally access the web page due to the user operation, based on the four-headed error code.

Substep 3: and if the exception type is the exception that the application program cannot normally access the webpage, generating and outputting information for prompting the exception that the application program cannot normally access the webpage.

In the above example, if the error code corresponding to the abnormality information of the HTTP application program interface is the quintet error code, the abnormality processing device generates and outputs information indicating an abnormality that the abnormality is an abnormality that the application program itself cannot normally access the web page, based on the quintet error code.

It should be noted that, in this embodiment, the reason why the application cannot normally access the web page is determined based on the mapping relationship between the error code and the exception type, and the corresponding prompt information is output, so that the technical effects of accuracy and reliability of the generated prompt information can be achieved, and the access experience of the user can be enhanced.

It should be noted that, in some embodiments, after determining the error code corresponding to the exception information of the second application program interface according to the preset mapping relationship between the exception information and the error code (i.e., step 1 included in S404 described above), a step of generating log information may be further included. For example, the step of generating log information may include:

step 1: and determining the alarm level corresponding to the error code corresponding to the abnormal information of the second application program interface according to the preset mapping relation between the error code and the alarm level.

In connection with the above example, the exception handling apparatus may set a mapping relationship between the error code and the alarm level in advance, for example, if the error code is a four-start error code, the alarm level may be set to a first level, and if the error code is a five-start error code, the alarm level may be set to a second level, and the alarm degree of the second level may be higher than that of the first level.

Step 2: and generating log information based on the abnormal information of the second application program interface and the determined alarm level.

It should be noted that, in this embodiment, by determining the alarm level and generating the log information according to the alarm level and the abnormal information, the richness of the log information can be increased, and the reliability of the log information can be improved, so that when the application program is subsequently completed and updated based on the log information, the accuracy and reliability of the completion and update can be improved, and the access experience of the user can be improved.

In order to further improve the comprehensiveness and richness of the log information, the content of the abnormal information can be further increased on the basis of generating the log information based on the abnormal information and the alarm level. For example, for different alarm levels, the exception information of the second application program interface may be redetermined, and may be embodied as:

for the higher level of alarm, the attribute information of the first application program interface may be obtained on the basis of the exception information of the second application program interface, and the log information may be generated in combination with the exception information of the second application program interface, the attribute information of the second application program interface, and the alarm level.

For the lower level of the alert level, log information may be generated directly based on the exception information and the alert level of the second application program interface.

It should be noted that, for any of the above embodiments, there may be a case where the abnormal information corresponding to the abnormal SQL is lost, and when the abnormal information corresponding to the abnormal SQL is lost, the abnormality processing device may obtain the abnormal information in a preset abnormal stack, and generate and output the prompt information according to the abnormal information in the preset abnormal stack.

The principle of generating and outputting the prompt information by the exception handling device according to the exception information in the preset exception stack is the same as that of generating and outputting the prompt information by the exception handling device according to the exception information corresponding to the abnormal SQL in any of the above embodiments, and is not described here again.

It should be noted that the preset exception stack is understood as a storage space in the exception handling apparatus, and may record and store each operation of the exception handling apparatus. In this embodiment, when the exception information corresponding to the exception SQL is lost, the exception handling apparatus generates and outputs the prompt information by combining the preset exception stack, so that the technical effects of flexibility, diversity, and reliability of generating and outputting the prompt information can be improved.

Referring to fig. 5, fig. 5 is a schematic diagram illustrating an exception handling apparatus of an application according to an embodiment of the present application.

As shown in fig. 5, the exception handling apparatus 500 of the application program includes:

the monitoring unit 501 is configured to monitor an application program accessing a web page, where the application program is generated based on a structured query language SQL.

The determining unit 502 is configured to determine, if an unidentifiable abnormal SQL of the application program is monitored, abnormal information corresponding to the abnormal SQL according to a preset columnar database, where the columnar database is a database storing the SQL.

A generating unit 503, configured to generate prompt information according to the abnormal information corresponding to the abnormal SQL, where the prompt information is used to prompt a reason why the application cannot normally access the webpage.

An output unit 504, configured to output the prompt information.

Referring to fig. 6, fig. 6 is a schematic diagram illustrating an exception handling apparatus of an application according to another embodiment of the present application.

As shown in fig. 6, the exception handling apparatus 600 for an application includes:

the monitoring unit 601 is configured to monitor an application that is accessing a web page, where the application is generated based on a structured query language SQL.

The determining unit 602 is configured to determine, if abnormal SQL of the application program is monitored, abnormal information corresponding to the abnormal SQL according to a preset columnar database, where the columnar database is a database storing SQL.

In some embodiments, the determining unit 602 is configured to determine, if the columnar database is abnormal, abnormal information corresponding to the abnormal SQL according to the abnormal columnar database, and if the columnar database is normal, determine the attribute information of the abnormal SQL as the abnormal information corresponding to the abnormal SQL.

As can be seen in conjunction with fig. 6, in some embodiments, the determining unit 602 includes:

an obtaining subunit 6021, configured to obtain abnormal content of the abnormal columnar database.

A third determining subunit 6022, configured to determine an abnormal code of the abnormal SQL according to the abnormal content.

A fourth determining subunit 6023, configured to determine, according to a preset mapping relationship between the abnormal code and the abnormal type, the abnormal type corresponding to the abnormal code of the abnormal SQL.

The processing subunit 6024 is configured to instantiate the exception type corresponding to the exception code of the exception SQL, so as to obtain exception information corresponding to the exception SQL.

The obtaining unit 603 is configured to obtain the abnormal information in the preset abnormal stack if the abnormal information corresponding to the abnormal SQL is lost, and use the abnormal information in the preset abnormal stack as the abnormal information corresponding to the abnormal SQL.

The generating unit 604 is configured to generate prompt information according to the abnormal information corresponding to the abnormal SQL, where the prompt information is used to prompt a reason why the application cannot normally access the webpage.

As can be seen from fig. 6, in some embodiments, if the application is an application of the first application interface, the generating unit 604 includes:

a first determining subunit 6041, configured to determine, according to a preset mapping relationship between the abnormality information of the first application program interface and the abnormality information of the second application program interface, that the abnormality information corresponding to the abnormal SQL corresponds to the abnormality information of the second application program interface.

A first generating sub-unit 6042 configured to generate prompt information according to the abnormality information of the second application program interface.

In some embodiments, the first generation subunit 6042 includes:

and the determining module is used for determining the error code corresponding to the abnormal information of the second application program interface according to the preset mapping relation between the abnormal information and the error code.

And the generating module is used for generating prompt information according to the error code corresponding to the abnormal information of the second application program interface.

In some embodiments, the generating module comprises:

the determining submodule is configured to determine, according to a preset mapping relationship between the error code and the exception type, an exception type corresponding to the error code corresponding to the exception information of the second application program interface, where the exception type includes: the application program is abnormal in that the application program cannot normally access the webpage due to user operation, and the application program itself is abnormal in that the webpage cannot normally access the webpage.

And the generation submodule is used for generating and outputting information for prompting that the abnormality is the abnormality that the application program cannot normally access the webpage caused by the user operation if the abnormality type is the abnormality that the application program cannot normally access the webpage caused by the user operation.

As can be seen in conjunction with fig. 6, in some embodiments, the generating unit 604 includes:

a second determining subunit 6043, configured to determine, according to a mapping relationship between preset error codes and alarm levels, an alarm level corresponding to an error code corresponding to the abnormal information of the second application program interface.

A second generating sub-unit 6044 for generating log information based on the abnormality information of the second application program interface and the determined alarm level.

An output unit 605 is configured to output the prompt information.

According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.

There is also provided, in accordance with an embodiment of the present application, a computer program product, including: a computer program, stored in a readable storage medium, from which at least one processor of the electronic device can read the computer program, the at least one processor executing the computer program causing the electronic device to perform the solution provided by any of the embodiments described above.

Fig. 7 is a block diagram of an electronic device according to an exception handling method of an application program according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.

As shown in fig. 7, the electronic apparatus includes: one or more processors 701, a memory 702, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 7, one processor 701 is taken as an example.

The memory 702 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by at least one processor, so that the at least one processor executes the exception handling method of the application program provided by the application program. The non-transitory computer-readable storage medium of the present application stores computer instructions for causing a computer to execute an exception handling method of an application program provided by the present application.

The memory 702, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the exception handling method of the application program in the embodiments of the present application. The processor 701 executes various functional applications of the server and data processing by running non-transitory software programs, instructions, and modules stored in the memory 702, that is, implements the exception handling method of the application program in the above-described method embodiment.

The memory 702 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the electronic device by the exception handling method of the application program, and the like. Further, the memory 702 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 702 may optionally include memory located remotely from the processor 701, and these remote memories may be connected to the application program exception handling method electronics via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The electronic device of the exception handling method of the application program may further include: an input device 703 and an output device 704. The processor 701, the memory 702, the input device 703 and the output device 704 may be connected by a bus or other means, and fig. 7 illustrates an example of a connection by a bus.

The input device 703 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic apparatus of the exception handling method of the application program, such as an input device of a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or the like. The output devices 704 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An exception handling method for an application program, comprising:

2. The method of claim 1, wherein if the application is an application of a first application program interface, generating and outputting a prompt message according to exception information corresponding to the exception SQL, comprising:

3. The method of claim 2, wherein generating and outputting a prompt message based on the exception information of the second application program interface comprises:

4. The method of claim 3, wherein generating and outputting the hint information based on an error code corresponding to the exception information for the second application program interface comprises:

5. The method of claim 4, after determining an error code corresponding to the exception information of the second application program interface according to a preset mapping relationship between the exception information and the error code, further comprising:

6. The method according to any one of claims 1 to 5, wherein determining the abnormal information corresponding to the abnormal SQL according to a preset column database comprises:

7. The method of claim 6, wherein determining exception information corresponding to the exception SQL from an exception columnar database comprises:

8. The method of any of claims 1 to 5, after determining exception information corresponding to the exception SQL from a preset columnar database, the method further comprising:

9. An exception handling apparatus for an application program, comprising:

the determining unit is used for determining abnormal information corresponding to the abnormal SQL according to a preset column database if the abnormal SQL which cannot be identified in the application program is monitored, wherein the column database is a database for storing the SQL;

and the output unit is used for outputting the prompt information.

10. An electronic device, comprising: a memory, a processor;

a memory; a memory for storing the processor-executable instructions;

wherein the processor is configured to perform the method of any one of claims 1 to 8.

11. A computer readable storage medium having stored therein computer executable instructions for implementing the method of any one of claims 1 to 8 when executed by a processor.

12. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 8.