CN112181696A - Abnormal information processing method, equipment and storage medium - Google Patents
Abnormal information processing method, equipment and storage medium Download PDFInfo
- Publication number
- CN112181696A CN112181696A CN202010900314.2A CN202010900314A CN112181696A CN 112181696 A CN112181696 A CN 112181696A CN 202010900314 A CN202010900314 A CN 202010900314A CN 112181696 A CN112181696 A CN 112181696A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- exception
- type
- user
- prompt information
- 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/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application provides an abnormal information processing method, abnormal information processing equipment and a storage medium. In some embodiments of the present application, a server receives user operation data sent by a user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method, a device, and a storage medium for processing exception information.
Background
At present, parameter verification is performed everywhere in a code, various abnormal conditions may be encountered in the running process of a system, some abnormal conditions need background processing and are sent to a page to prompt a user, but the system does not process the abnormal conditions. Therefore, the system has poor efficiency for exception handling and poor user experience.
Disclosure of Invention
Various aspects of the present application provide a method, device and storage medium for processing exception information, so as to improve the efficiency of system exception processing and improve user experience.
The embodiment of the application provides an abnormal information processing method, which is suitable for a server and comprises the following steps:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
The embodiment of the application provides an abnormal information processing method, which is suitable for a service end and comprises the following steps:
responding to input operation of a configuration user on an exception type, and acquiring the exception type;
and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information.
An embodiment of the present application provides a server, including: a memory and a processor;
the memory to store one or more computer instructions;
the processor to execute the one or more computer instructions to:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
Embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by one or more processors, causes the one or more processors to perform actions comprising:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
In some embodiments of the present application, a server receives user operation data sent by a user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic diagram of an exception information handling system according to an exemplary embodiment of the present application;
fig. 2a is a schematic flowchart of an exception information processing method according to an exemplary embodiment of the present application;
fig. 2b is a schematic flowchart of an exception information processing method according to an exemplary embodiment of the present application;
fig. 3 is a schematic structural diagram of a server according to an exemplary embodiment of the present application;
fig. 4 is a schematic structural diagram of a service end according to an exemplary embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
At present, parameter verification is performed everywhere in a code, various abnormal conditions may be encountered in the running process of a system, some abnormal conditions need background processing and are sent to a page to prompt a user, but the system does not process the abnormal conditions. Therefore, the system has poor efficiency for exception handling and poor user experience.
In some embodiments of the present application, a server receives user operation data sent by a user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram of an exception information processing system 10 according to an exemplary embodiment of the present application. As shown in fig. 1, the exception information handling system 10 includes a plurality of service terminals 10a, a service terminal 10b, and a user terminal 10 c. Among them, a plurality of service terminals 10a, user terminals 10c and service terminals 10b establish communication connection.
In the present embodiment, the plurality of service terminals 10a, the user terminal 10c and the service terminal 10b may be connected wirelessly or by wire. Optionally, the multiple service terminals 10a and the user terminal 10c may establish a communication connection with the service terminal 10b by adopting communication manners such as WIFI, bluetooth, infrared, and the like, or the multiple service terminals 10a and the user terminal 10c may also establish a communication connection with the service terminal 10b by using a mobile network. The network format of the mobile network may be any one of 2G (gsm), 2.5G (gprs), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4G + (LTE +), WiMax, and the like.
In this embodiment, the service end 10a is configured to respond to an input operation of a configuration user on an exception type, and obtain the exception type; and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information. The service end 10a includes an electronic display screen, which may be a computer device or a handheld device, and its implementation form may be various, for example, it may be a smart phone, a personal computer, a tablet computer, a smart sound box, and the like.
In the present embodiment, the user terminal 10c is used to display the abnormality prompting information for the user to view. The user terminal 10c includes an electronic display screen, which may be a computer device or a handheld device, and may be implemented in various forms, such as a smart phone, a personal computer, a tablet computer, a smart sound box, and the like.
In this embodiment, the server 10b performs parameter verification and exception handling by using an exception handling component. In this embodiment, the implementation form of the server 10b is not limited, and for example, the server 10b may be a server device such as a conventional server, a cloud host, a virtual center, and the like. The server 10b mainly includes a processor, a hard disk, a memory, a system bus, and the like, and a general computer architecture type.
It should be noted that, the information processing system 10 encapsulates the parameter verification and the exception handling corresponding to the service end 10a into a jar packet, so as to form an exception handling component. The exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process. Different clients 10a may introduce these jar packs into their respective code files and then may directly use the classes and attributes and methods in these jar packs. The codes among different service terminals are more uniform and standard, and parameter verification and exception handling of the whole system are processed by the exception handling component, so that the system is more convenient and faster.
Parameter verification is a common problem, and user input needs to be verified whether in a front-end or a background so as to ensure correctness of system data. The exception handling component carries out parameter verification and exception handling; wherein, when the parameter verification fails, the specific reason for the parameter verification failure also needs to be sent to the corresponding service end 10 a. The abnormal conditions of the system comprise service abnormality and system abnormality, and the service abnormality comprises but is not limited to the following: when logging in, the user name or password is wrong, and when a user is newly built, the account is already registered; system anomalies include, but are not limited to, the following: system crash, inter-service call failure, database exception, and memory overflow.
In this embodiment, the configuration user needs to establish a mapping relationship between the exception type and the exception prompting message through the service end 10 a. An optional embodiment is that the exception type is obtained in response to the input operation of the configuration user on the exception type; and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information. For example, when the parameter verification fails, detailed prompt information should be given to the user according to the reason why the parameter verification fails; when a service is abnormal, such as a user name or a password is wrong during login, an account is registered when a user is newly built, and the abnormality should give accurate prompt information to the user as much as possible, for example, "a user name is wrong, a password is wrong," an account is registered ", and the like; when a system fails, for example, the system crashes, the call between services fails, the database is abnormal, the memory overflows, the system abnormality can prompt a user for similar prompts such as "system abnormality, please contact an administrator" and the like, and specific prompt is not needed because the user does not care whether the service is abnormal or the database is abnormal, but the background log should record detailed error stack information so as to facilitate operation and maintenance or positioning problems of developers.
In this embodiment, the user operates through the user terminal 10c to generate user operation data, and the user terminal 10c sends the user operation data to the server 10 b; after receiving the user operation data sent by the user terminal 10c, the server 10b performs parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; and if the parameter verification result is that the verification is passed, continuously monitoring whether the system has an abnormal condition, and if the system has the abnormal condition, sending corresponding abnormal prompt information to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition. And if the parameter verification result is that the verification fails, sending verification exception prompt information to the corresponding service end.
In the above embodiment, if the system has an abnormal condition, according to the abnormal type of the abnormal condition, the corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type.
Optionally, if the system has system exception, intercepting the system exception by using an exception handling component; determining an exception type corresponding to system exception and first exception prompt information corresponding to the exception type; and sending first abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity. In addition, the server 10b may further send the first exception prompting message to a user terminal used by the user, so that the user can check the first exception prompting message.
Optionally, if the system has a business exception, capturing the business exception by using an exception handling component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity. In addition, the server 10b may further send the first exception prompting message to a user terminal used by the user, so that the user can check the first exception prompting message.
In the above embodiment, for the case that the first exception does not call the exception handling component to handle the exception, the exception handling component needs to actively catch the exception with the exception handling component to handle the exception. In one implementation, the server 10b monitors whether the exception handling component is utilized to handle the first exception; if not, capturing the first exception by using the exception handling component, and handling the first exception by using the exception handling component; the first anomaly is any one of abnormal conditions.
In the system embodiment of the present application, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
In addition to the exception information processing system 10 provided above, some embodiments of the present application also provide an exception information processing method, which may be implemented by depending on the exception information processing system 10, but is not limited to the exception information processing system 10 provided above.
From the perspective of the server, fig. 2a is a schematic flowchart of an exception information processing method provided in an exemplary embodiment of the present application. As shown in fig. 2a, the method comprises:
s211: receiving user operation data sent by a user terminal;
s212: performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter verification result is that the verification is passed, executing step S213, and if the parameter verification result is that the verification is not passed, executing step S214;
s213: continuing to monitor whether the system has an abnormal condition, if so, executing S215;
s214: sending a parameter checking abnormity prompt message to a corresponding service end;
s215: and sending corresponding abnormal prompt information to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition.
From the perspective of the service end, fig. 2b is a schematic flow chart of an abnormal information processing method according to an exemplary embodiment of the present application. As shown in fig. 2b, the method comprises:
s221: responding to the input operation of a configuration user on the exception type, and acquiring the exception type;
s222: and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information.
In this embodiment, the service end is configured to respond to an input operation of a configuration user on an exception type, and obtain the exception type; and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information. The service end includes an electronic display screen, which may be a computer device or a handheld device, and its implementation forms may be various, for example, it may be a smart phone, a personal computer, a tablet computer, a smart sound box, and the like.
In this embodiment, the user terminal is configured to display the exception prompt information for the user to view. The user terminal includes an electronic display screen, which may be a computer device or a handheld device, and its implementation forms may be various, for example, it may be a smart phone, a personal computer, a tablet computer, a smart sound box, and the like.
In this embodiment, the server performs parameter verification and exception handling by using the exception handling component. In this embodiment, the implementation form of the server is not limited, and for example, the server may be a server device such as a conventional server, a cloud host, and a virtual center. The server mainly comprises a processor, a hard disk, a memory, a system bus and the like, and a general computer architecture type.
It should be noted that, the information processing system 10 encapsulates the parameter verification and the exception handling corresponding to the service end into a jar packet, and forms an exception handling component. The exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process. Different service ends can introduce the jar packages into respective code files, and then the classes, the attributes and the methods in the jar packages can be directly used. The codes among different service terminals are more uniform and standard, and parameter verification and exception handling of the whole system are processed by the exception handling component, so that the system is more convenient and faster.
Parameter verification is a common problem, and user input needs to be verified whether in a front-end or a background so as to ensure correctness of system data. The exception handling component carries out parameter verification and exception handling; and when the parameter verification fails, the specific reason of the parameter verification failure needs to be sent to the corresponding service end. The abnormal conditions of the system comprise service abnormality and system abnormality, and the service abnormality comprises but is not limited to the following: when logging in, the user name or password is wrong, and when a user is newly built, the account is already registered; system anomalies include, but are not limited to, the following: system crash, inter-service call failure, database exception, and memory overflow.
In this embodiment, the configuration user needs to establish a mapping relationship between the exception type and the exception prompting message through the service end. An optional embodiment is that the exception type is obtained in response to the input operation of the configuration user on the exception type; and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information. For example, when the parameter verification fails, detailed prompt information should be given to the user according to the reason why the parameter verification fails; when a service is abnormal, such as a user name or a password is wrong during login, an account is registered when a user is newly built, and the abnormality should give accurate prompt information to the user as much as possible, for example, "a user name is wrong, a password is wrong," an account is registered ", and the like; when a system fails, for example, the system crashes, the call between services fails, the database is abnormal, the memory overflows, the system abnormality can prompt a user for similar prompts such as "system abnormality, please contact an administrator" and the like, and specific prompt is not needed because the user does not care whether the service is abnormal or the database is abnormal, but the background log should record detailed error stack information so as to facilitate operation and maintenance or positioning problems of developers.
In this embodiment, a user operates through a user terminal to generate user operation data, and the user terminal sends the user operation data to a server; after receiving the user operation data sent by the user terminal, the server performs parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; and if the parameter verification result is that the verification is passed, continuously monitoring whether the system has an abnormal condition, and if the system has the abnormal condition, sending corresponding abnormal prompt information to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition. And if the parameter verification result is that the verification fails, sending verification exception prompt information to the corresponding service end.
In the above embodiment, if the system has an abnormal condition, according to the abnormal type of the abnormal condition, the corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type.
Optionally, if the system has system exception, intercepting the system exception by using an exception handling component; determining an exception type corresponding to system exception and first exception prompt information corresponding to the exception type; and sending first abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity. In addition, the server side can also send first abnormal prompt information to the user terminal used by the user, so that the user can check the first abnormal prompt information.
Optionally, if the system has a business exception, capturing the business exception by using an exception handling component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity. In addition, the server side can also send first abnormal prompt information to the user terminal used by the user, so that the user can check the first abnormal prompt information.
In the above embodiment, for the case that the first exception does not call the exception handling component to handle the exception, the exception handling component needs to actively catch the exception with the exception handling component to handle the exception. One way to implement this is that the server monitors whether the first exception is handled by the exception handling component; if not, capturing the first exception by using the exception handling component, and handling the first exception by using the exception handling component; the first anomaly is any one of abnormal conditions.
In the embodiment of the method, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps S211 to S213 may be device a; for another example, the execution subject of steps S211 and S212 may be device a, and the execution subject of step S213 may be device B; and so on.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that these operations may be executed out of the order they appear herein or in parallel, and the order of the operations such as S211, S212, etc. is merely used to distinguish various operations, and the order itself does not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
Fig. 3 is a schematic structural diagram of a server according to an exemplary embodiment of the present application. As shown in fig. 4, the server includes: a memory 301 and a processor 302. In addition, the server also includes necessary components such as a power component 303 and a communication component 304.
The memory 301 is used for storing computer programs and may be configured to store other various data to support operations on the server. Examples of such data include instructions for any application or method operating on the server.
The memory 301, which may be implemented by any type of volatile or non-volatile memory device or combination thereof, may include, for example, Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A communication component 304 for data transmission with other devices.
Optionally, if the system has an abnormal condition, the processor 302 is specifically configured to, when sending corresponding abnormal prompt information to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition: if the system is abnormal, intercepting the system abnormality by using an abnormality processing component; determining an exception type corresponding to system exception and first exception prompt information corresponding to the exception type; and sending first abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity.
Optionally, the processor 302 is further operable to: and sending the first abnormal prompt information to a user terminal used by the user so that the user can check the first abnormal prompt information.
Optionally, if the system has an abnormal condition, when the processor 302 sends a corresponding abnormal prompt message to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the method is specifically configured to: if the system has business abnormity, capturing the business abnormity by utilizing an abnormity processing component; determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type; and sending second abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity.
Optionally, the processor 302 is further operable to: and sending second abnormal prompt information to the user terminal used by the user so that the user can check the second abnormal prompt information.
Optionally, the processor 302 is further operable to: monitoring whether the first exception is processed by the exception handling component; if not, capturing the first exception by using the exception handling component, and handling the first exception by using the exception handling component; the first anomaly is any one of abnormal conditions.
Optionally, the processor 302 is further operable to: and sending the parameter verification result and the abnormal condition to a monitoring platform so that the monitoring platform can monitor the parameter verification result and the abnormal condition.
Correspondingly, the embodiment of the application also provides a computer readable storage medium storing the computer program. The computer-readable storage medium stores a computer program, and the computer program, when executed by one or more processors, causes the one or more processors to perform the steps in the method embodiment of fig. 2 a.
Fig. 4 is a schematic structural diagram of a service end according to an exemplary embodiment of the present application. As shown in fig. 4, the service end includes: a memory 401 and a processor 402. In addition, the service end also includes necessary components such as a power component 403 and a communication component 404.
The memory 401 is used for storing computer programs and can be configured to store other various data to support operations on the service end. Examples of such data include instructions for any application or method operating on the business side.
The memory 401 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A communication component 404 for data transmission with other devices.
Correspondingly, the embodiment of the application also provides a computer readable storage medium storing the computer program. The computer-readable storage medium stores a computer program, and the computer program, when executed by one or more processors, causes the one or more processors to perform the steps in the method embodiment of fig. 2 b.
The communication components of fig. 3 and 4 described above are configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
The power supply components of fig. 3 and 4 described above provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.
In the embodiment of the method, the server receives user operation data sent by the user terminal; performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result; if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions; if the system has an abnormal condition, corresponding abnormal prompt information is sent to the service end corresponding to the abnormal type according to the abnormal type of the abnormal condition, the efficiency of system abnormal processing is high, and user experience is good.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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.
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.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
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 (10)
1. An abnormal information processing method is suitable for a server side, and is characterized by comprising the following steps:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
2. The method of claim 1, wherein if there is an abnormal situation in the system, sending a corresponding abnormal prompt message to the service end corresponding to the abnormal type according to the abnormal type of the abnormal situation, including:
if the system has system exception, intercepting the system exception by using an exception handling component;
determining an exception type corresponding to the system exception and first exception prompt information corresponding to the exception type;
and sending the first abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity.
3. The method of claim 2, further comprising:
and sending first abnormal prompt information to a user terminal used by a user so that the user can check the first abnormal prompt information.
4. The method of claim 1, wherein if there is an abnormal situation in the system, sending a corresponding abnormal prompt message to the service end corresponding to the abnormal type according to the abnormal type of the abnormal situation, including:
if the system has business abnormity, capturing the business abnormity by utilizing an abnormity processing component;
determining an abnormal type corresponding to the business abnormality and second abnormality prompt information corresponding to the abnormal type;
and sending second abnormity prompt information to a service end corresponding to the abnormity type corresponding to the system abnormity.
5. The method of claim 4, further comprising:
and sending second abnormal prompt information to a user terminal used by the user so that the user can check the second abnormal prompt information.
6. The method of claim 1, further comprising:
monitoring whether the first exception is processed by the exception handling component;
if not, capturing a first exception by using an exception handling component, and handling the first exception by using the exception handling component;
the first anomaly is any one of abnormal conditions.
7. The method of claim 1, further comprising:
and sending the parameter checking result and the abnormal condition to a monitoring platform so that the monitoring platform can monitor the parameter checking result and the abnormal condition.
8. An abnormal information processing method is suitable for a service end, and is characterized by comprising the following steps:
responding to input operation of a configuration user on an exception type, and acquiring the exception type;
and responding to the operation of the configuration user on the abnormal type configuration abnormal prompt information, and establishing the mapping relation between the abnormal type and the abnormal prompt information.
9. A server, comprising: a memory and a processor;
the memory to store one or more computer instructions;
the processor to execute the one or more computer instructions to:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by one or more processors, causes the one or more processors to perform acts comprising:
receiving user operation data sent by a user terminal;
performing parameter verification on the user operation data by using the created exception handling component to generate a parameter verification result;
if the parameter checking result is that the checking is passed, continuously monitoring whether the system has abnormal conditions;
if the system has an abnormal condition, sending corresponding abnormal prompt information to a service end corresponding to the abnormal type according to the abnormal type of the abnormal condition;
the exception handling component is packaged with exception handling classes, attributes and methods, and is used for parameter verification and centralized handling of exception conditions in the system working process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900314.2A CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900314.2A CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112181696A true CN112181696A (en) | 2021-01-05 |
| CN112181696B CN112181696B (en) | 2023-05-12 |
Family
ID=73924984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010900314.2A Active CN112181696B (en) | 2020-08-31 | 2020-08-31 | Abnormality information processing method, apparatus, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181696B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112764956A (en) * | 2021-01-14 | 2021-05-07 | 网宿科技股份有限公司 | Database exception handling system, and database exception handling method and device |
| CN115795387A (en) * | 2022-10-27 | 2023-03-14 | 圣名科技(广州)有限责任公司 | Sensor work abnormity monitoring method and device, storage medium and electronic equipment |
| CN116821000A (en) * | 2023-08-30 | 2023-09-29 | 天津租赁资产交易中心股份有限公司 | Method for processing abnormal operation of user feedback application |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6170067B1 (en) * | 1997-05-13 | 2001-01-02 | Micron Technology, Inc. | System for automatically reporting a system failure in a server |
| CN102043682A (en) * | 2011-01-27 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow exception handing method and system |
| CN102937930A (en) * | 2012-09-29 | 2013-02-20 | 重庆新媒农信科技有限公司 | Application program monitoring system and method |
| CN103269384A (en) * | 2013-06-14 | 2013-08-28 | 福建伊时代信息科技股份有限公司 | Rich client abnormality processing method, processing device and processing system |
| US20150242262A1 (en) * | 2014-02-26 | 2015-08-27 | Microsoft Corporation | Service metric analysis from structured logging schema of usage data |
| CN106610890A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Exception processing method and apparatus |
| CN108121633A (en) * | 2016-11-30 | 2018-06-05 | 北京国双科技有限公司 | Exception catching method and device |
| CN109257196A (en) * | 2017-07-12 | 2019-01-22 | 阿里巴巴集团控股有限公司 | A kind of abnormality eliminating method and equipment |
| CN109344046A (en) * | 2018-08-09 | 2019-02-15 | 北京奇艺世纪科技有限公司 | A kind of data processing method, device, medium and electronic equipment |
| CN109726081A (en) * | 2019-01-02 | 2019-05-07 | 深圳壹账通智能科技有限公司 | Method, apparatus, computer equipment and the storage medium of service exception processing |
| CN110149343A (en) * | 2019-05-31 | 2019-08-20 | 国家计算机网络与信息安全管理中心 | A kind of abnormal communications and liaison behavioral value method and system based on stream |
| CN110166297A (en) * | 2019-05-22 | 2019-08-23 | 平安信托有限责任公司 | O&M method, system, equipment and computer readable storage medium |
| US10394691B1 (en) * | 2017-10-05 | 2019-08-27 | Tableau Software, Inc. | Resolution of data flow errors using the lineage of detected error conditions |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
-
2020
- 2020-08-31 CN CN202010900314.2A patent/CN112181696B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6170067B1 (en) * | 1997-05-13 | 2001-01-02 | Micron Technology, Inc. | System for automatically reporting a system failure in a server |
| CN102043682A (en) * | 2011-01-27 | 2011-05-04 | 中国农业银行股份有限公司 | Workflow exception handing method and system |
| CN102937930A (en) * | 2012-09-29 | 2013-02-20 | 重庆新媒农信科技有限公司 | Application program monitoring system and method |
| CN103269384A (en) * | 2013-06-14 | 2013-08-28 | 福建伊时代信息科技股份有限公司 | Rich client abnormality processing method, processing device and processing system |
| US20150242262A1 (en) * | 2014-02-26 | 2015-08-27 | Microsoft Corporation | Service metric analysis from structured logging schema of usage data |
| CN106610890A (en) * | 2015-10-21 | 2017-05-03 | 北京国双科技有限公司 | Exception processing method and apparatus |
| CN108121633A (en) * | 2016-11-30 | 2018-06-05 | 北京国双科技有限公司 | Exception catching method and device |
| CN109257196A (en) * | 2017-07-12 | 2019-01-22 | 阿里巴巴集团控股有限公司 | A kind of abnormality eliminating method and equipment |
| US10394691B1 (en) * | 2017-10-05 | 2019-08-27 | Tableau Software, Inc. | Resolution of data flow errors using the lineage of detected error conditions |
| CN109344046A (en) * | 2018-08-09 | 2019-02-15 | 北京奇艺世纪科技有限公司 | A kind of data processing method, device, medium and electronic equipment |
| CN109726081A (en) * | 2019-01-02 | 2019-05-07 | 深圳壹账通智能科技有限公司 | Method, apparatus, computer equipment and the storage medium of service exception processing |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
| CN110166297A (en) * | 2019-05-22 | 2019-08-23 | 平安信托有限责任公司 | O&M method, system, equipment and computer readable storage medium |
| CN110149343A (en) * | 2019-05-31 | 2019-08-20 | 国家计算机网络与信息安全管理中心 | A kind of abnormal communications and liaison behavioral value method and system based on stream |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112764956A (en) * | 2021-01-14 | 2021-05-07 | 网宿科技股份有限公司 | Database exception handling system, and database exception handling method and device |
| CN112764956B (en) * | 2021-01-14 | 2024-01-12 | 网宿科技股份有限公司 | Database exception handling system, database exception handling method and device |
| CN115795387A (en) * | 2022-10-27 | 2023-03-14 | 圣名科技(广州)有限责任公司 | Sensor work abnormity monitoring method and device, storage medium and electronic equipment |
| CN116821000A (en) * | 2023-08-30 | 2023-09-29 | 天津租赁资产交易中心股份有限公司 | Method for processing abnormal operation of user feedback application |
| CN116821000B (en) * | 2023-08-30 | 2023-12-12 | 天津租赁资产交易中心股份有限公司 | Method for processing abnormal operation of user feedback application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112181696B (en) | 2023-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112181696B (en) | Abnormality information processing method, apparatus, and storage medium | |
| CN109857404B (en) | SDK interface packaging method and device, storage medium and electronic equipment | |
| CN112788128B (en) | Business information pushing method and device, storage medium and electronic device | |
| CN110932918B (en) | Log data acquisition method and device and storage medium | |
| CN112187616A (en) | Message sending method, device and storage medium | |
| CN111367760B (en) | Log collection method and device, computer equipment and storage medium | |
| EP3099011A1 (en) | Interface management service entity, functional service entity and network element management method | |
| CN109656572A (en) | Packaging method and device, computer equipment, the storage medium of installation kit | |
| CN109951326B (en) | Data processing method, device, storage medium and processor | |
| CN114356434B (en) | Page loading method, device, apparatus, storage medium and program product | |
| CN107644075A (en) | The method and apparatus for collecting page info | |
| CN105099769A (en) | Method, device and system for processing abnormal operations of service platform | |
| CN111967850A (en) | Data reporting monitoring method and device and electronic equipment | |
| CN111222592A (en) | Method and device for acquiring two-dimensional code of equipment | |
| CN109982315B (en) | Log uploading method and related equipment | |
| CN114553608A (en) | Method and device for accessing cloud platform | |
| CN109686017A (en) | A kind of tax controlling equipment management method and system | |
| CN102946594B (en) | Method for automatically obtaining equipment information in Telematics system during using navigation with one key | |
| CN114168183A (en) | Front-end resource information processing method, device, equipment and storage medium | |
| CN113094268B (en) | Test method, test device, test equipment and test medium | |
| CN107566519A (en) | A kind of code operation method, apparatus, server and server cluster | |
| CN109902113B (en) | Credit feedback report processing method and device, storage medium and computer equipment | |
| CN113934552A (en) | Method and device for determining function code, storage medium and electronic device | |
| CN112835766A (en) | Application monitoring method and device | |
| EP2950566B1 (en) | Method, device and terminal for binding nfc application and operator |
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 |