CN106897185B - Method and device for outputting abnormity - Google Patents
Method and device for outputting abnormity Download PDFInfo
- Publication number
- CN106897185B CN106897185B CN201610535043.9A CN201610535043A CN106897185B CN 106897185 B CN106897185 B CN 106897185B CN 201610535043 A CN201610535043 A CN 201610535043A CN 106897185 B CN106897185 B CN 106897185B
- Authority
- CN
- China
- Prior art keywords
- node
- abnormal information
- abnormal
- information
- exception
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3068—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data format conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a method and a device for outputting exception, in the method, a node can convert data contained in exception information sent by a previous node into data in a standard format through a preset format conversion rule, the node can determine the specific content of the abnormal information when determining that the received information is the abnormal information, and correspondingly, since the data in the exception information has been converted by the node in format into a data format recognizable by each node, therefore, when other subsequent nodes receive the converted abnormal information, the specific content of the abnormal information can be determined, so that the identified abnormal information is presented to the user after certain processing, and further, the problem that maintenance personnel or users of online services cannot check abnormal information due to the fact that the nodes cannot identify the abnormal information sent by other nodes is avoided.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for outputting an exception.
Background
In order to meet the increasing living demands of people, currently, various online services with powerful functions and simple operation are successively provided by a plurality of online platforms, and are presented to users in the form of websites, applications (apps) and the like.
The abnormal operation condition of each service inevitably occurs in the actual operation, generally, the abnormal operation occurring in the service processing process can be roughly divided into two types, the first type is called system self-abnormal, the abnormal operation is usually caused by the server (system) itself operating the service, for example, the server (system) itself has operation failure to finally cause the abnormal operation, or the server (system) itself has the conditions such as service logic error, service code error and the like to cause the abnormal operation in the process of processing the service; the second type is called non-system self exception, which generally means that in practical application, during the process of running the service, a server (system) sometimes needs to call other servers (systems) to complete the processing work of the service, and if during the call process, the other servers (systems) have situations such as running failure, processing the error of the service, and the like, the exception of the service also occurs.
For the two types of exceptions described above, in general, when the service is abnormal, a server (system) running the service generally needs to capture the abnormal information, and output the captured abnormal information after certain processing, so as to present the abnormal information to a maintenance person or a user of the online service. For the second type of abnormality, in a normal case, when another server (system) called by the server (system) is abnormal, the abnormal information generated by the other server (system) for the abnormal occurrence is sent to the server (system), and after the server (system) receives the abnormal information sent by the other server (system) (which is equivalent to capturing the abnormal information), the specific content of the abnormal information can be identified, and the identified result is presented to a maintenance person or a user of the online service for viewing.
For example, suppose that a service a needs to be processed by a server (system) B and a server (system) a in sequence, and then the server (system) a finally outputs a processing result, where an abnormality occurs when the server (system) B processes the service a, the server (system) B may generate abnormality information corresponding to the abnormality for the occurred abnormality, and send the abnormality information to the server (system) a, and after receiving the abnormality information sent by the server B (which is equivalent to capturing the abnormality information), the server (system) a may identify specific content of the abnormality information, and present the identified result to a maintenance person or a user of the online service.
However, in practical applications, the data contained in the exception information sent by each server (system) often differs in format, and if the server (system) running the service does not have a protocol for converting the exception information agreed with other servers (systems), when the server (system) receives the abnormal information sent by other servers (systems), since the data contained in the abnormality information may not be in a format that can be recognized by the server (system), therefore, even if the server (system) receives the abnormality information, the abnormality information cannot be recognized, that is, the server (system) can determine that the received information is abnormal information, but cannot determine the specific content of the abnormal information, therefore, the abnormal information cannot be processed and output, which brings difficulty to maintenance personnel or users of online business in the process of viewing the abnormal information.
Disclosure of Invention
The embodiment of the application provides a method for outputting exception, which is used for solving the problem that in the prior art, the inconvenience is brought to maintenance personnel or users of online services in the process of checking exception information.
The embodiment of the application provides a device for outputting exception, which is used for solving the problem that in the prior art, inconvenience is brought to maintenance personnel or users of online services in the process of checking exception information.
The embodiment of the application adopts the following technical scheme:
the embodiment of the application provides a method for outputting exception, which comprises the following steps:
the first node receives abnormal information sent by the second node;
judging whether the format of the data contained in the abnormal information is a standard format or not;
if yes, outputting the abnormal information;
if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and outputting the converted abnormal information.
The embodiment of the application provides a method for outputting exception, which comprises the following steps:
the conversion node receives the abnormal information sent by the first node;
judging whether the format of the data contained in the abnormal information is a standard format or not;
if so, sending the abnormal information to a second node;
if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and sending the converted abnormal information to the second node.
The embodiment of the present application provides an output abnormal device, including:
the receiving module is used for receiving the abnormal information sent by the second node;
the judgment output module judges whether the format of the data contained in the abnormal information is a standard format; if yes, outputting the abnormal information; if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and outputting the converted abnormal information.
The embodiment of the present application provides an output abnormal device, including:
the information receiving module is used for receiving the abnormal information sent by the first node;
the judging and sending module is used for judging whether the format of the data contained in the abnormal information is a standard format or not; if so, sending the abnormal information to a second node; if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and sending the converted abnormal information to the second node.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
in the embodiment of the application, a node can convert data contained in abnormal information sent by a previous node into data in a standard format through a preset format conversion rule, so that the node can determine the received information as the abnormal information and can also determine the specific content of the abnormal information, correspondingly, since the data in the abnormal information is converted into a data format which can be recognized by each node by the node in the format, when the converted abnormal information is received by other subsequent nodes, the specific content of the abnormal information can also be determined, so that the recognized abnormal information is presented to a user after certain processing, and further, the problem that maintenance personnel or the user of online service cannot see the abnormal information due to the fact that the node cannot recognize the abnormal information sent by other nodes is avoided, and the transmission efficiency of the abnormal information is improved, and the resources of each node are saved.
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 process for output exceptions provided by embodiments of the present application;
fig. 2 is a schematic diagram of an arrangement of interceptors provided in an embodiment of the present application;
fig. 3 is a schematic view of a service link provided with a unified interceptor according to an embodiment of the present application;
FIG. 4 is a method for output exception, implemented by middleware, provided by an embodiment of the present application;
fig. 5 is a schematic diagram of a service link including a switching node according to an embodiment of the present application;
fig. 6 is a schematic view of a service link provided with a plurality of conversion nodes according to an embodiment of the present application;
fig. 7 is a schematic diagram of a service link including a conversion node and an interceptor according to an embodiment of the present application;
FIG. 8 is a schematic diagram of an apparatus for outputting an exception according to an embodiment of the present application;
fig. 9 is a schematic diagram of another apparatus for output abnormality according to an 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.
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 process of outputting an exception according to an embodiment of the present application, which specifically includes the following steps:
s101: and the first node receives the abnormal information sent by the second node.
In practical applications, a plurality of nodes are often required to perform a service, in other words, after a node receives a service request sent by a user, it is usually required to invoke other nodes to perform processing of the service request, and no matter the node receiving the service request or the other nodes, when processing the service request, there may be a case of an abnormal operation, where the abnormal operation may be caused by operating conditions of the node itself on one hand, and on the other hand, may be caused by conditions such as a service logic error, a service code error and the like occurring when the node processes the service request.
For the case of an abnormality, in order to enable a maintainer or a user of an online service to know what kind of abnormality occurs in the execution process of the service by checking the abnormality information corresponding to the abnormality, when an abnormality occurs in the process of processing the service request by a node, it is usually necessary to generate corresponding abnormality information for the occurred abnormality and output the abnormality information, where if the node is a node that finally outputs a service processing result on a service link, after capturing the abnormality and generating the corresponding abnormality information, the node may output the abnormality information to be presented to the maintainer or the user of the online service for checking. However, since the embodiment of the present application is intended to solve the problem that the node cannot identify the abnormal information sent by other nodes, so that the abnormal information cannot be presented to the online service maintenance personnel or users, for the case that the node is not the final node on the service link (i.e. the node is not the node that finally outputs the service processing result), when the node has an abnormality during the process of executing the service request, the node may capture the abnormality and generate the abnormal information corresponding to the abnormality, and then the node may send the abnormal information to the next node corresponding to the node on the service link, for convenience of subsequent description, in the embodiment of the present application, the node that generates the abnormal information may be referred to as a second node, and the node that receives the abnormal information sent by the second node may be referred to as a first node, so when the second node sends the generated abnormal information to the first node, the first node will also correspondingly receive the abnormal information sent by the second node.
It should be noted that, the node mentioned here may be a server or a system on a service link, that is, there are multiple servers or systems on the service link, and after a service request sent by a user needs to be processed by the multiple servers or systems on the service link, a service processing result is finally output by the server or system that finally outputs the service processing result on the service link. Besides, the node mentioned in the embodiment of the present application may also be a processing unit or a processing module in a server, that is, each node in the service link may be formed by each processing unit or processing module included in a server, where these processing units or processing modules may be software such as a program, besides hardware devices. Of course, each node on the traffic link may be configured by a plurality of servers or each processing unit or processing module included in the system.
S102: and judging whether the format of the data contained in the abnormal information is a standard format, if so, executing step S103, and if not, executing step S104.
S103: and outputting the abnormal information.
S104: and converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and outputting the converted abnormal information.
In practical applications, the Exception information generated by the service node for the occurred Exception generally includes data such as an error code and an error description in addition to the basic Exception information, for example, two of system. overflow Exception and Format Exception are the basic Exception information included in the Exception information, and the information such as 0x80040277 belongs to the error code information included in the Exception information. In other words, the basic exception information included in the exception information is often the same for different nodes, and each node can usually recognize the basic exception information included in the exception information, so that when a node receives information including the exception information, it can usually determine that the received information is exception information according to the exception information. However, data such as error codes, error descriptions, etc. contained in the anomaly information generated by different nodes for the same anomaly may be different for data such as error codes, error descriptions, etc. contained in the anomaly information generated by different nodes for the same anomaly, for example, for an anomaly occurring in the service a, the error code contained in the anomaly information generated by the node a for the anomaly may be 0x79996730, while for a node B, the error code contained in the anomaly information generated by the node B for the anomaly may be 0x73236012, so that when the node a sends the anomaly information generated by the node a for the anomaly to the node B, since the error code generated by the node B for the anomaly is different from that of the node a, after the node B receives the anomaly information, the node B can determine that the information is an anomaly information by the basic anomaly type information contained in the anomaly information, however, since the data such as the error code in the abnormal information cannot be identified, the node B cannot further determine the specific content of the abnormal information, and further cannot process the abnormal information.
In general, a conversion protocol is pre-agreed between nodes for the same exception, that is, for two nodes agreed to convert the same exception in advance, when a node sends exception information generated for the exception to another node, the other node can convert data such as error codes and error descriptions contained in the exception information into data such as error codes and error descriptions which can be recognized by the other node according to the pre-agreed conversion protocol, and further recognize the converted data such as error codes and error descriptions to determine the specific content of the exception information. However, in practical applications, the nodes and nodes only preset the protocol for conversion for some exceptions, and for an exception without the protocol for conversion agreed in advance, when one node sends the exception information generated for such an exception to another node, since the two nodes do not agree in advance with the protocol for conversion for the exception, after receiving the exception information, the other node cannot recognize data such as error codes and error descriptions included in the exception information, and accordingly cannot determine the specific content of the exception information.
Therefore, in order to avoid the above problem, in this embodiment of the present application, each node may also set a format conversion rule for itself, and when receiving the abnormal information sent by another node, according to a preset format conversion rule for itself, convert data included in the abnormal information into data that can be recognized by itself, and further obtain converted abnormal information that can be recognized by itself, where the format conversion rule mentioned here may be: the node can convert the same abnormal information sent by different nodes into uniform abnormal information which can be recognized by the node through the format conversion rule, and the node can convert all the abnormal information into the abnormal information which can be recognized by the node through the format conversion rule, unlike the prior art which only aims at a part of the abnormal information.
For example, there are U, I, O three service nodes on a service link, each node has a set of format conversion rules for itself, so when an abnormality occurs in the process of performing a service by a node U, the abnormal information generated for the abnormality can be sent to the node I, and the node I finds out after receiving the abnormal information sent by the node U that the format of the data contained in the abnormal information is not the standard format required by itself, so the node I can convert the data contained in the abnormal information into the data that can be recognized by itself according to the preset set of format conversion rules for itself and send the converted abnormal information to the subsequent node O, and accordingly, the node O finds out after receiving the converted abnormal information sent by the node I that the format of the data contained in the converted abnormal information is not the standard format required by itself, therefore, the node O can convert the data in the standard format specified by the corresponding node I, which is included in the converted abnormal information, into the data in the standard format specified by the node O according to a preset set of format conversion rules for the node O, and finally output the converted abnormal information, wherein, the format conversion rule preset in each node can be a set of complete corresponding relation between the standard format of all nodes and the standard format of the node, if the abnormal information and the service processing result received by each node on the service link are all sent by the fixed node, that is, the call relationship between nodes on the service link is fixed, and the format conversion rule preset in each node may be a corresponding relationship between a standard format specified by itself and a standard format specified by a node having a fixed call relationship with itself.
However, in general, the call relationship between the nodes is not always fixed, for example, for a service, after receiving a service request sent by a user, the node 1 often needs to determine, through the content of the identified service request, to which node the service request needs to be sent subsequently to continue processing, so for two service requests, although the two service requests are received by the node 1, if the contents of the two service requests are different, the node 1 may also send the two service requests to different nodes, correspondingly, if an abnormality occurs in the process of processing the service request by the node 1, it is often necessary to determine to which node the generated abnormal information should be sent according to the content of the service request, that is, the node 1 generally corresponds to a plurality of nodes, therefore, for the node 1, in order to enable the node corresponding to it (node 1) to recognize the abnormal information sent by itself (node 1), the node 1 needs to respectively agree with the format conversion rules of the nodes corresponding to it in advance, and each format conversion rule is usually only applicable to two nodes agreed with each other, so that not only is the transmission complexity of the abnormal information greatly increased (i.e. since the format conversion rules are agreed with each other between the nodes, the abnormal information needs to be converted once when arriving at one node), but also each node needs to store the format conversion rules agreed with other nodes, so that the more nodes on the service link are, the more format conversion rules each node needs to store in advance, the more storage space of each node is occupied, and at the same time, the abnormal information needs to be converted once when arriving at one node, this greatly increases the resource consumption of each node, thereby reducing the transmission efficiency of the abnormal information.
In order to avoid the above problem, in this embodiment of the present application, each node may preset the same format conversion rule, and identify each data (e.g., data such as error code, error description, etc.) included in the abnormal information through the format conversion rule, in a subsequent process, when the node receives the abnormal information sent by another node, the node may convert the format of the data included in the abnormal information into a standard format according to the preset format conversion rule, and output the converted abnormal information, so that after receiving the converted abnormal information, since the format of the data included in the abnormal information is already the converted standard format, the other node may identify the data included in the abnormal information, and further determine the specific content of the abnormal information, and at the same time, the abnormal information is converted abnormally without passing through each node, the converted abnormal information can be recognized by the subsequent nodes only through one-time conversion, so that the transmission efficiency of the abnormal information is greatly improved, the resources of the nodes are saved, and the storage space of each node is saved.
Specifically, after receiving the abnormal information sent by the second node, the first node may determine whether a format of data included in the abnormal information is a standard format, if so, it may be determined that the abnormal information has undergone standard conversion, and then directly output the abnormal information, and when the first node determines that the format of the data included in the abnormal information is not the standard format, in order to ensure that a subsequent node can effectively identify the data included in the abnormal information, the first node may convert the data included in the abnormal information into the data in the standard format according to a preset format conversion rule, wherein during the conversion process of the data format, the first node may determine an abnormal type of the abnormal information first, and this is intended that, in practical applications, the abnormality captured by the node is generally divided into a plurality of abnormal types, for different abnormal information of the same abnormal type, the data such as error codes, error descriptions and the like contained in each abnormal information are often different from each other, in other words, the abnormal information is usually divided into a plurality of abnormal categories, the different abnormal information belongs to the abnormal categories respectively, for the preset format conversion rule, if the format conversion rule is not classified according to the abnormal type, but a uniform format conversion rule is set for all the abnormal information, the node does not record the conversion relations of all the data such as the error codes, the error descriptions and the like and the standard data one by one according to the categories, correspondingly, when the node performs format conversion on the data in the abnormal information subsequently, the node traverses the preset conversion relations and performs format conversion on the data in the abnormal information after finding, therefore, for this situation, if the more data conversion relationships recorded in the preset format conversion rule, the longer the time for the node to traverse the data conversion relationships, and the lower the efficiency of converting data.
Therefore, in order to avoid the above situation, in the embodiment of the present application, the online service maintainer may set different format conversion rules for different exception types, where different format conversion rules may correspond to exception information of one exception type, and then the online service maintainer may enter each format conversion rule set for different exception types into each node. Correspondingly, each node stores each preset format conversion rule in advance, so that before the first node converts the abnormal information sent by the second node, the first node can determine the abnormal type of the abnormal information, then the first node can determine the format conversion rule corresponding to the abnormal type in each preset format conversion rule according to the determined abnormal type, and after the corresponding format conversion rule is determined, convert the data contained in the abnormal information into the data in the standard format, and output the converted abnormal information.
It should be noted that after looking at the abnormal information finally output by the node, the maintenance personnel of the online service generally needs to know who the abnormal information is generated, in other words, the whole service is executed, and then a problem occurs at which service node, therefore, in this embodiment of the application, after receiving the abnormal information sent by the second node, the first node may create an error stack corresponding to the abnormal information for the abnormal information, and push the node identifier corresponding to the second node into the error stack, and output the abnormal information, where the node identifier mentioned here may be a server identifier, a system identifier, or an identifier of a processing unit, a processing module, or the like, and furthermore, the pushing of the node identifier corresponding to the second node mentioned here into the error stack does not mean that the abnormal information is generated by the second node (i.e. it does not mean that an abnormality occurs in the second node), the exception information received by the first node is sent by the second node regardless of whether the exception information is generated by the second node, and correspondingly, if the subsequent first node needs to send the exception information to the third node again (the third node is the next node of the first node on the service link), the third node can also push the node identifier corresponding to the first node into the error stack and output the exception information. Therefore, maintenance personnel of the online service can subsequently sort out the whole service link by checking the error stack, find out the source of the abnormality on the service link according to the node identification recorded in the error stack and correspondingly repair the abnormality, wherein the node identifications are sequentially pressed into the error stack, so that when only one abnormality occurs in the service execution process, the node identification positioned at the lowest position in the error stack is the source of the abnormality in the service execution process.
It should be further noted that, in a general case, if the second node is a source node where an exception occurs, the first node may create an error stack corresponding to the exception information when receiving the exception information sent by the second node, and the error stack is attached to the exception information in an information form and output to a next node, and accordingly, after receiving the exception information sent by the first node, the next node may push a node identifier corresponding to the first node into the error stack in the exception information and output to the next node until outputting the exception information to a final node on the service link. For the error stacks in the information form, the error stacks generated by different nodes may also have different information formats, and therefore, in the embodiment of the present application, a maintenance worker of the online service may also set a uniform conversion rule for the error stacks in the information form, and enter the conversion rule into each node, and when a subsequent node receives the abnormal information sent by another node, finds that the error stacks in the information form included in the abnormal information do not conform to the preset standard format in format, the error stacks in the information form may be converted into the error stacks in the standard format according to the preset conversion rule, and the error stacks in the information form after conversion are attached to the abnormal information for output. In this way, since the format of the converted error stack is a standard format that each node can recognize, subsequent nodes can recognize the error stack in the information form, and the node identifier corresponding to the previous node is pushed into the error stack to complete the update work of the error stack.
In general, the exception types of the exception information can be generally divided into two categories, where the first category refers to an exception type for a service aspect, and the second category refers to some common exception types, such as network connection exception, and the like. For the two major types of exception types, in the embodiment of the present application, the node may only convert the exception information of the first type of exception type, and for the exception information of the second type of exception type, the node may not capture the exception information of the first type of exception type, but send the exception information of the first type of exception type to a specified interceptor for unified processing. The specific implementation process can be as follows: after receiving the abnormal information sent by the second node, the first node may first determine whether the abnormal type of the abnormal information is a specified abnormal type, where the specified abnormal type refers to the above-mentioned first-type abnormal type, that is, for the abnormal type in the business aspect, when the first node determines that the abnormal type of the abnormal information is the specified abnormal type, the first node may convert the data contained in the abnormal information into data in a standard format according to a preset format conversion rule and output the converted abnormal information, and when the first node determines that the abnormal type of the abnormal information is not the specified abnormal type, that is, the abnormal type of the abnormal information is the second-type abnormal type (common abnormal type), the first node may send the abnormal information to the subsequent node until the abnormal information is intercepted by a preset interceptor and converted into the abnormal information in the standard format for output, as shown in fig. 2.
Fig. 2 is a schematic diagram of a setting of an interceptor according to an embodiment of the present disclosure.
In fig. 2, the interceptor is disposed before the final node E on the traffic link, so that when the node B (the first node) finds that the abnormal information sent by the node a (the second node) has an abnormal type that is not the specified abnormal type (i.e. the common abnormal type), the node B can send the abnormal information to the node C, and correspondingly, when the node C finds that the abnormal information has an abnormal type that is not the specified abnormal type after receiving the abnormal information, the node C can send the abnormal information to the subsequent node until the abnormal information is transmitted to the interceptor, the interceptor can convert the abnormal information into the abnormal information in the standard format and send the converted abnormal information to the node E, so that the node E can output the converted abnormal information after receiving the converted abnormal information, for viewing by maintenance personnel or users of the online service.
It should be noted that the position of the interceptor may also be set at other positions, such as between node B and node C in fig. 2, or between node C and node D, and there is no fixed limit to the number of interceptors, and one interceptor may be set between every two nodes, so as to ensure that, in the process of executing a service, even if different common exceptions (i.e., exceptions of the second type) occur in each node, each interceptor can accurately intercept different exception information occurring in each node, and convert the exception information into exception information of a standard format and output the exception information to subsequent nodes. Certainly, in order to save resources, for the case that different common exceptions occur in multiple nodes, a uniform interceptor may be set, and each node sends exception information to the interceptor before sending the exception information to the next node, and the interceptor sends the processed exception information to the subsequent node, as shown in fig. 3.
Fig. 3 is a schematic view of a service link provided with a unified interceptor according to an embodiment of the present application.
In fig. 3, when an abnormality occurs at node a, the abnormal information generated for the abnormality may be sent to node b, and after receiving the abnormal information sent by node a, node b finds that the type of the abnormality of the abnormal information b is not the specified type of the abnormality (that is, the type of the abnormality of the abnormal information is a common type of the abnormality), so node b may send the abnormal information to the interceptor. After receiving the abnormal information, the interceptor can convert the format of the data contained in the abnormal information into a standard format according to a preset format conversion rule, and send the converted abnormal information to the node c, because the abnormal information is usually carried in a processing result obtained after the node itself processes a service request, in order to prevent the node c from generating an abnormality in the process of processing the service request, the node c can send the processing result carrying the abnormal information to the interceptor after receiving the processing result sent by the node c, the interceptor can filter the abnormal information in the processing result, and judge whether the data contained in the filtered abnormal information of the common abnormal type is the data of the standard format, if so, the abnormal information is previously subjected to the standard conversion processing by the interceptor, if not, it indicates that the exception information has not been subjected to standard conversion processing by the interceptor previously, in other words, since the node c is not the initial node on the service link shown in fig. 3, the exception information of the common exception type sent by the node c received by the interceptor should be generated by the node c itself, that is, the node c has a common exception during processing the service request, and accordingly generates the exception information of the common exception type. Therefore, the abnormal information of each common abnormal type converted by the uniform interceptor can be effectively identified by the final node e on the service link, and the effective output of the abnormal information by the final node e is further ensured.
It should be noted that the interceptor described above may be a stand-alone device, such as a server, a terminal, etc., and of course, the interceptor may also be a unit or a module in the server or the terminal, etc.
In practical applications, if a Service request sent by a user can be completed only by processing one node, even if an exception occurs in the process of processing the Service request by the node, the node does not need to convert exception information corresponding to the exception, and therefore, the method described in the embodiment of the present application should be implemented on the premise that one Service request is completed after being processed by a plurality of nodes, and therefore, the method for outputting the exception provided in the embodiment of the present application should be suitable for a scenario of multi-node call, such as a Service-Oriented Architecture (SOA).
It can be seen from the above method that, since the node can convert the data contained in the abnormal information into the data in the standard format recognizable by each node, after receiving the converted abnormal information, other subsequent nodes can also identify the data contained in the abnormal information to determine the specific content of the abnormal information, thereby effectively avoiding the problem that the maintenance personnel or users of the online service cannot check the abnormal information due to the fact that the node cannot identify the abnormal information sent by other nodes, bringing convenience to the maintenance personnel or users of the online service when checking the abnormal information, and since the abnormal information can be identified by other nodes only by converting once, the transmission efficiency of the abnormal information is greatly improved, and the resources of each node are saved.
In the method described above, the data in the abnormal information is converted into the data in the standard format by each node, and in order to improve the efficiency of the node in processing the service request and save the resources of the node, a dedicated middleware for performing the abnormal information conversion may be provided, and each node is ensured to recognize the received abnormal information through the middleware, which will be described in detail below.
Fig. 4 is a method for outputting an exception, implemented by a middleware, provided in an embodiment of the present application, specifically including the following steps:
s401: and the conversion node receives the abnormal information sent by the first node.
In this embodiment of the present application, in order to ensure that each node on a service link can effectively identify abnormal information generated by each node, a conversion node may be provided to convert data included in the abnormal information generated by each node into data in a standard format and output the data, where the conversion node mentioned here is the above-mentioned middleware dedicated to data format conversion, and therefore, in this embodiment of the present application, after generating the abnormal information, a first node may attach the abnormal information to a processing result obtained after processing a service request sent by a user by itself and send the processing result to the conversion node, and accordingly, in order to ensure that a subsequent node on the service link can identify the abnormal information generated by the first node, the conversion node needs to receive the abnormal information sent by the first node, as shown in fig. 5.
Fig. 5 is a schematic view of a service link including a switching node according to an embodiment of the present application.
In fig. 5, when an exception occurs when a node X processes a service request sent by a user, the node X may generate corresponding exception information for the occurred exception, and send the exception information to a conversion node, and accordingly, the conversion node needs to receive the exception information sent by the node X to ensure that the exception information can be successfully transmitted on the service link subsequently.
Of course, in the embodiment of the present application, a switching node may also be disposed between every two nodes on the traffic link, as shown in fig. 6.
Fig. 6 is a schematic view of a service link provided with multiple conversion nodes according to an embodiment of the present application.
In fig. 6, a conversion node is arranged between every two nodes on the service link, so that when an abnormality occurs in the process of processing a service request sent by a user, the node X can send abnormal information generated for the abnormality to the node Y through the conversion node, and when the abnormal information passes through the conversion node between the node X and the node Y, the conversion node can convert data contained in the abnormal information (abnormal information) into data in a standard format and output the converted abnormal information, so that after the node Y receives the abnormal information, the specific content of the abnormal information can be effectively determined while confirming that the information is abnormal information, and the node Y can be further ensured to smoothly transmit the converted abnormal information to a subsequent node. Moreover, because one conversion node is arranged between every two nodes, when the node Y is abnormal in the process of executing the service, the abnormal information generated aiming at the abnormality of the node Y can be sent to the subsequent conversion node, so that after the conversion node receives the abnormal information sent by the node Y, the data in the abnormal information can be converted into the data in the standard format, and the converted abnormal information is sent to the subsequent node, thereby ensuring that each node on the service link can effectively identify the abnormal information sent by the previous node, and further ensuring the final output of the abnormal information.
It should be noted that the first node and the second node mentioned later are different from the first node and the second node mentioned in step S101, the first node mentioned in step S101 is for receiving the exception information, the second node is for sending the exception information, the first node mentioned in step S401 is for sending the exception information, and the second node mentioned later is for receiving the exception information, and it should be distinguished here and not confused.
S402: and judging whether the format of the data contained in the abnormal information is a standard format, if so, executing step S403, and if not, executing step S404.
S403: and sending the abnormal information to a second node.
S404: and converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and sending the converted abnormal information to the second node.
After receiving the abnormal information sent by the first node, the conversion node may determine whether a format of data included in the abnormal information is a standard format, if so, it may be determined that the abnormal information has been previously converted, and the abnormal information may be directly sent to the second node, and if it is found that the format of data included in the abnormal information is not the standard format, it may be determined that the abnormal information has not been previously converted, and the data included in the abnormal information may be converted into data in the standard format according to a preset format conversion rule, where a specific conversion process may be: the conversion node may determine an exception type of the exception information, and determine a format conversion rule corresponding to the exception type in a preset format conversion rule according to the determined exception type, and then, the conversion node may convert data, such as an error code, an error description, and the like, included in the exception information into data in a standard format according to the determined format conversion rule, and send the converted exception information to the second node, where the detailed process is as described in steps S202 to S204 above, and is not described herein again.
It should be noted that, when the conversion node determines that the data included in the abnormal information sent by the first node is already data in the standard format, the abnormal information may be directly sent to the second node, or the abnormal information may be returned to the first node, and the first node sends the abnormal information to the second node. For the converted abnormal information, the conversion node not only directly sends the converted abnormal information to the second node, but also returns the converted abnormal information to the first node, and the first node sends the converted abnormal information to the second node, that is, the converted abnormal information is sent to the second node through the first node.
In addition, in this embodiment of the present application, after receiving the exception information sent by the node for the first time, the conversion node may create a corresponding error stack for the exception information, and push the node identifier that sent the exception information into the error stack, and after receiving the exception information sent by another node, the subsequent conversion node may also push the node identifiers of the other nodes into the error stack in sequence according to the receiving order, so that a maintainer of a subsequent online service may determine which node on the service link has an exception to the end by checking the error stack stored by the conversion node, and then repair the exception.
In the embodiment of the present application, one interceptor may also be set for the common exception information of the exception type, so that the conversion node (middleware) and the interceptor are respectively responsible for the conversion work of the exception information of different exception types, as shown in fig. 7.
Fig. 7 is a schematic diagram of a traffic link including a conversion node and an interceptor according to an embodiment of the present application.
In fig. 7, when receiving the abnormal information sent by another node, the node may send the abnormal information to the conversion node, and after receiving the abnormal information, the conversion node may determine whether the abnormal information is abnormal information of a specified abnormal type (i.e. a first type of abnormality: abnormality for a service), if so, further determine whether the data included in the abnormal information is data of a standard format, and when determining that the data included in the abnormal information is data of a non-standard format, convert the data included in the abnormal information into data of a standard format and output the converted abnormal information according to a preset format conversion rule, and when finding that the abnormal information sent by the conversion node is not the abnormal information of a specified abnormal type (i.e. it is determined that the abnormal type of the abnormal information is an abnormality of a second type: common abnormality), the abnormal information can be directly output until the abnormal information is transmitted to the interceptor, and the interceptor intercepts the abnormal information and converts the data in the abnormal information into data in a standard format for output. Since the interceptor for processing the common abnormal type abnormal information is arranged in the service link shown in fig. 7, the operation burden of the conversion node is greatly reduced, and the resources of the conversion node are saved.
Based on the same idea, the method for outputting an exception provided in the embodiment of the present application further provides a device for outputting an exception, as shown in fig. 8 and 9.
Fig. 8 is a schematic diagram of an apparatus for outputting an abnormal condition according to an embodiment of the present application, which specifically includes:
a receiving module 801, configured to receive exception information sent by a second node;
a judgment output module 802, which judges whether the format of the data included in the abnormal information is a standard format; if yes, outputting the abnormal information; if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and outputting the converted abnormal information.
The device further comprises:
a creating module 803 that creates an error stack corresponding to the exception information; and pushing the node identification of the second node into the error stack, and outputting the abnormal information.
The judgment output module 802 determines the abnormal type of the abnormal information; determining a format conversion rule corresponding to the abnormal type in preset format conversion rules according to the abnormal type; and converting the data contained in the abnormal information into data in a standard format according to the determined format conversion rule, and outputting the converted abnormal information.
The judgment output module 802 judges whether the exception type of the exception information is a specified exception type; if the abnormal type is the appointed abnormal type, converting the data contained in the abnormal information into the data in the standard format according to a preset format conversion rule; and if the abnormal information is not in the specified abnormal type, sending the abnormal information to a subsequent node until the abnormal information is intercepted by a preset interceptor and converted into the abnormal information in the standard format for output.
The device is used for outputting the abnormal information in the service-oriented architecture SOA.
Fig. 9 is a schematic diagram of another apparatus for output abnormality according to an embodiment of the present application.
A receive information module 901, which receives the abnormal information sent by the first node;
a determining and sending module 902, configured to determine whether a format of data included in the abnormal information is a standard format; if so, sending the abnormal information to a second node; if not, converting the data contained in the abnormal information into data in a standard format according to a preset format conversion rule, and sending the converted abnormal information to the second node.
The determining and sending module 902 is configured to send the abnormal information to the second node through the first node;
the determining and sending module 902 sends the converted abnormal information to the second node through the first node.
The embodiment of the application provides a method and a device for outputting exception, in the method, a node can convert data contained in exception information sent by a previous node into data in a standard format through a preset format conversion rule, so that the node can determine the specific content of the exception information while determining that the received information is the exception information, correspondingly, because the data in the exception information is converted into a data format which can be recognized by the node, when other subsequent nodes receive the converted exception information, the specific content of the exception information can also be determined, the recognized exception information is presented to a user after certain processing, and the problem that maintenance personnel or the user of online service cannot see the exception information due to the fact that the node cannot recognize the exception information sent by other nodes is avoided, and the transmission efficiency of the abnormal information is improved, and the resources of each node are saved.
It should be noted that the execution subjects of the steps of the method provided in embodiment 1 may be the same device, or different devices may be used as the execution subjects of the method. For example, the executing agent of step S101 and step S102 may be a receiving module in the first node, and the executing agent of step S103 may be a sending module of the first node; for another example, the execution subject of step 101 may be a receiving module in the first node, and the execution subjects of step 102 and step 103 may be a judgment output module of the first node; and so on.
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.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The 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 (12)
1. A method of outputting an exception, comprising:
a first node receives abnormal information sent by a second node, wherein the abnormal information corresponds to an error stack, and identifiers of the second node are sequentially recorded in the error stack;
judging whether the format of the data contained in the abnormal information is a standard format or not;
if yes, outputting the abnormal information;
if not, determining the abnormal type of the abnormal information, determining a format conversion rule corresponding to the abnormal type in a preset format conversion rule according to the abnormal type, converting data contained in the abnormal information into data in a standard format according to the determined format conversion rule, and outputting the converted abnormal information.
2. The method of claim 1, wherein the method further comprises:
creating an error stack corresponding to the exception information;
and pushing the node identification of the second node into the error stack, and outputting the abnormal information.
3. The method according to claim 1, wherein converting the data included in the abnormal information into data in a standard format according to a preset format conversion rule specifically includes:
judging whether the abnormal type of the abnormal information is a specified abnormal type;
if the abnormal type is the appointed abnormal type, converting the data contained in the abnormal information into the data in the standard format according to a preset format conversion rule;
and if the abnormal information is not in the specified abnormal type, sending the abnormal information to a subsequent node until the abnormal information is intercepted by a preset interceptor and converted into the abnormal information in the standard format for output.
4. The method of claim 1, wherein the method is for exception information output in a service oriented architecture, SOA.
5. A method of outputting an exception, comprising:
a conversion node receives abnormal information sent by a first node, wherein the abnormal information corresponds to an error stack, and the error stack is sequentially recorded with an identifier of the first node;
judging whether the format of the data contained in the abnormal information is a standard format or not;
if so, sending the abnormal information to a second node;
if not, determining the abnormal type of the abnormal information, determining a format conversion rule corresponding to the abnormal type in a preset format conversion rule according to the abnormal type, converting data contained in the abnormal information into data in a standard format according to the determined format conversion rule, and sending the converted abnormal information to the second node.
6. The method of claim 5, wherein sending the exception information to a second node specifically comprises:
sending the abnormal information to the second node through the first node;
sending the converted abnormal information to the second node, specifically including:
and sending the converted abnormal information to the second node through the first node.
7. An apparatus for outputting an abnormality, comprising:
the receiving module is used for receiving abnormal information sent by a second node, the abnormal information corresponds to an error stack, and the error stack is sequentially recorded with an identifier of the second node;
the judgment output module judges whether the format of the data contained in the abnormal information is a standard format; if yes, outputting the abnormal information; if not, determining the abnormal type of the abnormal information, determining a format conversion rule corresponding to the abnormal type in a preset format conversion rule according to the abnormal type, converting data contained in the abnormal information into data in a standard format according to the determined format conversion rule, and outputting the converted abnormal information.
8. The apparatus of claim 7, wherein the apparatus further comprises:
a creating module that creates an error stack corresponding to the exception information; and pushing the node identification of the second node into the error stack, and outputting the abnormal information.
9. The apparatus according to claim 7, wherein the determination output module determines whether the abnormality type of the abnormality information is a specified abnormality type; if the abnormal type is the appointed abnormal type, converting the data contained in the abnormal information into the data in the standard format according to a preset format conversion rule; and if the abnormal information is not in the specified abnormal type, sending the abnormal information to a subsequent node until the abnormal information is intercepted by a preset interceptor and converted into the abnormal information in the standard format for output.
10. The apparatus of claim 7, wherein the apparatus is for exception information output in a Service Oriented Architecture (SOA).
11. An apparatus for outputting an abnormality, comprising:
the information receiving module is used for receiving abnormal information sent by a first node, the abnormal information corresponds to an error stack, and the error stack is sequentially recorded with an identifier of the first node;
the judging and sending module is used for judging whether the format of the data contained in the abnormal information is a standard format or not; if so, sending the abnormal information to a second node; if not, determining the abnormal type of the abnormal information, determining a format conversion rule corresponding to the abnormal type in a preset format conversion rule according to the abnormal type, converting data contained in the abnormal information into data in a standard format according to the determined format conversion rule, and sending the converted abnormal information to the second node.
12. The apparatus of claim 11, wherein the determining sending module sends the exception information to the second node via the first node;
and the judging and sending module is used for sending the converted abnormal information to the second node through the first node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610535043.9A CN106897185B (en) | 2016-07-08 | 2016-07-08 | Method and device for outputting abnormity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610535043.9A CN106897185B (en) | 2016-07-08 | 2016-07-08 | Method and device for outputting abnormity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106897185A CN106897185A (en) | 2017-06-27 |
| CN106897185B true CN106897185B (en) | 2020-04-24 |
Family
ID=59191577
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610535043.9A Active CN106897185B (en) | 2016-07-08 | 2016-07-08 | Method and device for outputting abnormity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106897185B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108196971A (en) * | 2017-12-29 | 2018-06-22 | 北京五八信息技术有限公司 | A kind of analysis method of data, device, terminal and storage medium |
| CN109254986A (en) * | 2018-08-31 | 2019-01-22 | 阿里巴巴集团控股有限公司 | A kind of determination method and device of abnormal data |
| CN109343993A (en) * | 2018-09-28 | 2019-02-15 | 郑州云海信息技术有限公司 | A kind of error message processing method and processing device of cloud platform |
| CN111181759B (en) * | 2019-08-08 | 2021-09-14 | 腾讯科技（深圳）有限公司 | Method, device, equipment and storage medium for identifying abnormality of network equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930370B (en) * | 2010-09-09 | 2013-04-03 | 上海普元信息技术股份有限公司 | System structure for realizing data conversion in service integration of SOA (Service Oriented Architecture) application system and method thereof |
| CN103491135A (en) * | 2013-09-02 | 2014-01-01 | 用友软件股份有限公司 | Device and method for conducting self-matching on data formats |
| CN104935499A (en) * | 2015-05-28 | 2015-09-23 | 杭州华三通信技术有限公司 | Message format conversion method and equipment |
| KR20160008292A (en) * | 2014-07-14 | 2016-01-22 | 주식회사 팬더아이앤씨 | Payment certification server using decoded division code |
| CN105512022A (en) * | 2014-09-25 | 2016-04-20 | 华为技术有限公司 | Method and device for data processing |
-
2016
- 2016-07-08 CN CN201610535043.9A patent/CN106897185B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930370B (en) * | 2010-09-09 | 2013-04-03 | 上海普元信息技术股份有限公司 | System structure for realizing data conversion in service integration of SOA (Service Oriented Architecture) application system and method thereof |
| CN103491135A (en) * | 2013-09-02 | 2014-01-01 | 用友软件股份有限公司 | Device and method for conducting self-matching on data formats |
| KR20160008292A (en) * | 2014-07-14 | 2016-01-22 | 주식회사 팬더아이앤씨 | Payment certification server using decoded division code |
| CN105512022A (en) * | 2014-09-25 | 2016-04-20 | 华为技术有限公司 | Method and device for data processing |
| CN104935499A (en) * | 2015-05-28 | 2015-09-23 | 杭州华三通信技术有限公司 | Message format conversion method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106897185A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106897185B (en) | Method and device for outputting abnormity | |
| CN105207806A (en) | Monitoring method and apparatus of distributed service | |
| CN111552568B (en) | Cloud service calling method and device | |
| CN110969417A (en) | Government affair item synchronization method, device, system, computer equipment and storage medium | |
| CN112422361A (en) | Switch testing method, device and medium | |
| CN116055524A (en) | Interaction method, processor and device for Internet platform and Internet of things equipment | |
| US20170011302A1 (en) | Action correlation framework | |
| CN106571975B (en) | Fault tolerance method and device for communication data | |
| CN114040032A (en) | Protocol conversion method, system, storage medium and electronic equipment | |
| CN112765246B (en) | Task processing method, device, electronic equipment and storage medium | |
| CN113411209A (en) | Distributed password service full-link detection system and method | |
| CN113094269A (en) | Application program test exception analysis method and device | |
| CN115037653B (en) | Service flow monitoring method, device, electronic equipment and storage medium | |
| CN107766232B (en) | Plug-in management method and device | |
| CN114022279A (en) | Service data error correction method, device, equipment and readable storage medium | |
| CN113778726A (en) | Error information processing method, device, server and storage medium | |
| CN114691395A (en) | Fault processing method and device, electronic equipment and storage medium | |
| CN113810379A (en) | Exception handling method and multi-service system | |
| EP3756310B1 (en) | Method and first node for managing transmission of probe messages | |
| CN114637555B (en) | General method for obtaining logistics information in batches | |
| CN113094268B (en) | Test method, test device, test equipment and test medium | |
| CN111368512B (en) | Service data conversion method, device, equipment and storage medium | |
| CN117876112A (en) | Transaction request processing method and device, storage medium and electronic equipment | |
| CN114721811A (en) | Distributed processing method, system and device | |
| US10628803B1 (en) | Dial home optimizer |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |