CN100574221C - A kind of multisystem error code management method, Apparatus and system - Google Patents
A kind of multisystem error code management method, Apparatus and system Download PDFInfo
- Publication number
- CN100574221C CN100574221C CN200710307753.7A CN200710307753A CN100574221C CN 100574221 C CN100574221 C CN 100574221C CN 200710307753 A CN200710307753 A CN 200710307753A CN 100574221 C CN100574221 C CN 100574221C
- Authority
- CN
- China
- Prior art keywords
- error
- platform
- message
- service system
- global
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 24
- 238000000034 method Methods 0.000 claims abstract description 24
- 238000012545 processing Methods 0.000 claims description 58
- 238000006243 chemical reaction Methods 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 12
- 230000003993 interaction Effects 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 2
- 230000008569 process Effects 0.000 description 11
- 230000000739 chaotic effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000012856 packing Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000007596 consolidation process Methods 0.000 description 1
- 238000013497 data interchange Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000000873 masking effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of multisystem error code management method, Apparatus and system, solve the error message confusion of directly returning by the data transaction platform at present, the problem of bringing debugging difficulty and user to obscure.Described method comprises: receive service system message and parsing, if comprise error message, then add in the global error structure; Error identification according to platform inside has judged whether the platform internal error, if having, then adds in the global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of external error sign indicating number, convert described platform internal error to external error, and add in the global error structure then.Described error message is organized return code by different level according to the order of service system mistake, platform external error, internal error, thereby realized multiple service system mistake and platform errors are returned to client by different level, the client user can find wrong spot at an easy rate when debugging, can not cause and obscure.
Description
Technical field
The present invention relates to data processing technique, particularly relate to a kind of multisystem error code management method and device.
Background technology
In large-scale data handling system, for improving data sharing and data-handling efficiency, a data conversion platform usually is set connects other each service systems, and the data processing between two service systems need be passed through this data transaction platform.With reference to shown in Figure 1, be the logical architecture figure of described large data treatment system.This data handling system is provided with multiple service system 11 according to service needed, and every kind of service system 11 is responsible for different Business Processing, and transfer of data between the service system 11 and Business Processing are undertaken by data transaction platform 12.Data transaction platform 12 is as the intermediate link of Business Processing, connecting a plurality of service systems 11, be used for receiving service request from miscellaneous service client 13, and be transmitted to corresponding service system 11 processing, the response message that each service system 11 is returned returns to client 13 simultaneously.
Participate in the process of data processing in a plurality of service systems, mutual frequent between each service system and the data transaction platform, the entire process process may be because multiple former thereby produce various error messages, the mistake that mistake that produces comprising service system and platform self-operating produce.For the mistake that service system produces, service system can reflect the result of service system in the mode of return code (comprising error message), and returns to corresponding client by platform.And platform is when returning various error messages to client, because platform does not have good mismanage mechanism, only carry out forwarding capability simply, various error messages are left intact, so the return code of service system and the error message that self produces can be obscured and send to client together, cause return information chaotic and redundant, cause that the client user obscures.Perhaps, error message is lost as fruit part, and the service system mistake will mask platform errors, causes concrete wrong spot to be covered, and brings difficulty to debugging.
For example, in the interdepartmental system real-time deal of financial sector, accept certain professional client (being meant various preposition terminals, as ATM, POS machine, preposition sales counter etc.) and deliver easy request on the data transaction platform, this request needs service system A and service system B to handle jointly.Platform at first is forwarded to request service system A and handles, and A returns result, and platform is transmitted to service system B with the result of A again and proceeds to handle, and at last the result of B is returned to client, finishes the trading processing process.In this process, if service system A and B and platform have all produced error message, platform can all be obscured all error messages and returns to client together, like this client user just can't to distinguish which mistake be that platform produces, which mistake is that service system A produces, and which is again that the B of system produces.Perhaps, platform falls the error masking that self produces when returning error message, and the client user does not just know that some mistake is caused by platform like this.
Therefore, above-mentioned relating under the mutual situation of a plurality of systems and data interchange platform,, platform is very chaotic to the management of error message, and the error code that returns by platform masks platform errors easily, cause the debugging difficulty, and chaotic information causes easily that also the user obscures.
Summary of the invention
Technical problem to be solved by this invention provides a kind of multisystem error code management method, Apparatus and system, to solve the error message confusion of directly returning by the data transaction platform at present, and the problem of bringing debugging difficulty and user to obscure.
For solving the problems of the technologies described above,, the invention discloses following technical scheme according to specific embodiment provided by the invention:
A kind of multisystem error code management method is applied to the mutual of data transaction platform and a plurality of service systems, comprising:
The data transaction platform receives the service system message and resolves, if comprise error message, then adds in the global error structure;
According to the error identification of platform inside, judged whether the platform internal error, if having, then add in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Message is formed in error message in the described global error structure sent to client.
Wherein, service system mistake and platform internal error are added to before the global error structure, also comprise: convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.
Wherein, message is formed in error message also comprised before:, the error message in the global error structure is mapped in the message structure of relative client definition according to the different definition of different clients to message structure.
Preferably, described message is according to the der group bag of service system mistake, platform external error, platform internal error.
Described method also comprises: adopt the unusual nested mechanism of JDK, return error message according to the interaction sequences layering of different service systems and platform.
A kind of multisystem error code management devices is arranged on the data transaction platform, comprising:
Service system fault processing unit is used to receive service system message and parsing, if comprise error message, then adds in the global error structure;
The platform errors processing unit is used for the error identification according to platform inside, has judged whether the platform internal error, if having, then adds in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Error code returns the unit, is used for that message is formed in all error messages of described global error structure and sends to client.
Preferably, described device also comprises: format conversion unit, be used for converting service system mistake and platform internal error to unified error format respectively, and then adding in the global error structure according to the calling of described service system fault processing unit and platform fault processing unit.
Wherein, described error code returns the unit earlier according to the different definition of different clients to message structure, the error message in the global error structure is mapped in the message structure of relative client definition, and then forms the message transmission.
Wherein, described error code returns the unit and returns error message according to the order of service system mistake, platform external error, platform internal error.
Wherein, described error code returns the unit and adopts the unusual nested mechanism of JDK, returns error message according to the interaction sequences layering of different service systems and platform.
A kind of error code management system comprises data transaction platform and a plurality of service system, and with the mutual client of data transaction platform, wherein, described data transaction platform comprises:
Service system fault processing unit is used to receive service system message and parsing, if comprise error message, then adds in the global error structure;
The platform errors processing unit is used for the error identification according to platform inside, has judged whether the platform internal error, if having, then adds in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Error code returns the unit, is used for that message is formed in all error messages of described global error structure and sends to client.
Wherein, described data transaction platform also comprises: format conversion unit, be used for calling according to described service system fault processing unit and platform fault processing unit, convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.
Wherein, described error code returns the unit and returns error message according to the order of service system mistake, platform external error, platform internal error.
According to specific embodiment provided by the invention, the invention discloses following technique effect:
The embodiment of the invention provides a kind of multisystem error code administrative mechanism, adopt layering to organize wrong return code, by various error message classification are handled, respectively service system mistake, platform internal error and external error are added in the global error structure, then the error message in the global error structure is organized return code by different level according to the order of service system mistake, platform external error, internal error, thereby realized multiple service system mistake and platform errors are returned to client by different level.Owing to clearly identified details such as error source, error reason in the error code that returns, the client user can find wrong spot at an easy rate when debugging, can not cause and obscure.
And at the different problem of error code form that each service system is returned, platform is also changed according to consolidation form the service system mistake, returns to different clients with the error code laminated tissue of self then together.If service system and platform make a mistake simultaneously, because client user's more attention is the error message of service layer, so preferentially the service system mistake is returned.
Description of drawings
Fig. 1 is the logical architecture figure of the medium-and-large-sized data handling system of prior art;
Fig. 2 is the described multisystem error code management method of an embodiment of the invention flow chart;
Fig. 3 is the described multisystem error code of an embodiment of the invention management devices structured flowchart;
Fig. 4 is the described error code management system of an embodiment of the invention structure chart.
Embodiment
For above-mentioned purpose of the present invention, feature and advantage can be become apparent more, the present invention is further detailed explanation below in conjunction with the drawings and specific embodiments.
Under many service systems environment, the problem of the error code confusion that the data transaction platform returns to client, the embodiment of the invention provides a kind of error code administrative mechanism for platform, adopt layering to organize wrong return code, by various error message classification are handled, respectively with the service system mistake, platform internal error and external error are added in the global error structure, then with the error message in the global error structure according to the service system mistake, platform external error, the order of internal error is organized return code by different level, thereby has realized multiple service system mistake and platform errors are returned to client by different level.To be that example describes below with the trading processing of financial field.
In the present embodiment, at first error message is classified, be divided into service system mistake, platform internal error and external error.Wherein, hereinafter the service system mistake is referred to as application error because service system is responsible for Business Processing, reflection be the mistake of service layer, for example " amount of money " though field does not have mistake technically, may not satisfy operational requirement and makes mistakes.And platform is responsible for data transaction, does not relate to Business Processing, reflection be mistake on the technological layer.Platform errors is divided into internal error and external error again, and the platform internal error is the error description mode that is used for platform self, and external error is the error description mode that returns to various clients, is convenient to the user and understands.The describing mode of these two kinds of mistakes is different with presentation format, need change, and their contrast relationship is described in the error code configuration.
With reference to Fig. 2, be described multisystem error code management method flow chart.
Carry out in the process of trading processing in service system,, then error message is returned to the data transaction platform with the message form if make a mistake.Wherein, type of error, error code, error description, mistake field data etc. have been write down in described error message, and described wrong field data is to the replenishing of error description, and is used to describe the wrong context that takes place, and helps by the daily record misarrangement.For example, certain transaction of certain is unpacked and is made mistakes, and " unpacking and make mistakes " so belongs to error description, and " client " and " transaction " belongs to the mistake field data.
After step 202, platform are received the message that service system returns, carry out the processing of unpacking of service system message, thereby carry out packet parsing.
Usually, wrong if service system is handled, can in returned packet, identify, platform can judge whether wrong by this sign.If have, then execution in step 204; If no, then service system is not made mistakes in the trading processing process, forwards step 205 to.
The error message of extracting from the returned packet of service system comprises type of error, error code, error description etc., and these information are added in the global error structure.Described global error structure is used to preserve various error messages, comprises the application error of service system generation, internal error and the external error that platform produces.
Preferably, add to application error in the global error structure before, earlier convert application error to unified error format, and then add in the global error structure.Because each service system that links to each other with platform all has himself information processing manner and fault processing mode, so the reflection system handles result's that these systems return error code all has different data formats.Platform need be changed the service system mistake according to the data format of internal unity, and then add in the global error structure for the ease of internal data management.
Because platform is an intermediate system, finally be to realize by different service systems for the realization of Business Processing.The major function that platform service is handled is the service call of realizing different service systems, and provides new service by the mode of mapping and service combination to client, and the data of being responsible for producing when different service systems are called are simultaneously carried out consistency and handled.
For example: each service processing function in the service system (as card disassemble family, deposit, withdraw the money, client's income inquiry etc.) all can be issued into one or one group of corresponding service in platform.Service processing is exactly that the service of calling these issues realizes service call to different service systems.
Simultaneously, service processing module also will guarantee the data consistency handled.For example: the client forwards a fund to account B from account A, and platform can call the service of withdrawing the money earlier from account A deduction fund, calls the deposit service again and deposits fund in account B.Serve successfully if withdraw the money, and the deposit service causes the inconsistency of data owing to the network reason is interrupted, service processing module will just be dashed the service of withdrawing the money automatically so, just cancels the service processing to account A, guarantees the consistency of data.
In the whole data transaction and processing procedure of platform and service system, service system and platform all might produce error message, therefore after having judged whether the service system number has application error, need also to judge whether platform inside makes a mistake.During judgement, judge whether wrongly according to the error identification of platform self,, then continue step 207 if having; If no, then platform does not make a mistake, and forwards step 210 to.
The present invention does not do qualification to the judgement order of using wrong and platform internal error, and above-mentioned steps only describes as embodiment, can adjust according to different service application.
The error message of extracting from the data processing of information of platform self comprises type of error, error code, error description etc., and these information are also added in the global error structure.Equally, preferred, internal error information also converts uniform data format earlier to, and then adds to the global error structure.
This step is the preferred steps of present embodiment, because internal error is the error description mode that is used for platform inside, can't discern for preposition terminal uses such as ATM, POS, cabinet faces, therefore need convert the describing mode that the platform external staff can discern understanding to, i.e. external error.The corresponding relation of platform internal error and external error is described in the error code configuration in advance, thereby, can the internal error sign indicating number be generated the external error sign indicating number according to the error code configuration.
Step 209 is also added external error in the global error structure.
At this moment, if mistake has all taken place for service system and platform, preserved the description of application error, platform internal error and external error in the then described global error structure.Various error description notice relative client in the global error structure can be finished fault processing, and follow-up step is the detailed description as embodiment.
Step 210 is added the global error structure to the uniform data district.
Described uniform data district is the zone that is used to deposit various data processed result in the present embodiment, comprise Various types of data such as the various error messages that produce in the data handling procedure, business datum, system's control data, according to user's difference setting, these data can return to client for user inquiring.
Step 211 is shone upon conversion with the error message in the described uniform data district according to the message structure that different clients defines.
In practical business, the message structure that different clients requires to return is different, comprises the different of data format and message field (MFLD) definition, and for example ATM is a kind of message format, and preposition sales counter is again another kind of message structure.Therefore, at different clients, the error message of returning need be mapped in the corresponding message structure.
After error message carried out message mapping conversion, form the message bag and return to corresponding client.Preferably, present embodiment is according to the sequential organization message of application error, platform external error, internal error, because when service system and platform make a mistake simultaneously, because client user's more attention is the mistake of service layer, so preferentially the application error that service system is produced returns, and platform external error is easier to understand to the user than internal error, so next returning to external mistake.This multi-level error code returns form, for user's debugging provides convenience greatly.
The processing mode that the above-mentioned platform errors sign indicating number administrative mechanism information that is left intact with platform, directly carries out is transmitted is compared, organize wrong return code owing to adopt layering, realized multiple service system mistake and platform errors are returned to client by different level, the client user can find wrong spot at an easy rate when debugging, can not cause and obscure, can not cover any mistake yet.And, the service system return code of different-format is unified, be convenient to of the management of platform inside to various misdatas.
The layered mode of above-mentioned service system application error, platform external error, internal error is to handle according to the layering that error source carries out, and in the present embodiment, can understand from a plurality of angles the error code layering.For example, when needing to call a plurality of service systems in the same trading processing process and handle,, then return error code in turn according to the interaction sequences of service system and platform if there are a plurality of systems to make a mistake.
Illustrate, certain strides the real-time deal of two systems, and this transaction is served transaction request from client C, sends to service system A after the platform processes, and A returns response message to platform after finishing Business Processing, and platform extracts return code (error code) from response message.Then, again this transaction is sent to service system B and process, same platform also extracts return code (error code) from its return information.At last, platform organizes return code (error code) to return to client C according to the disposition of external system and the disposition of native system according to layering.
On technology realizes, the layering that the embodiment of the invention adopts is based on the unusual nested mechanism of JDK, and JDK is the abbreviation of Java Development Kit, and JDK is the core of whole Java, be the basis of all java application programs, all java application programs all are structured on the JDK.
The abnormality processing of JDK is unique formal error reporting mechanism among the Java.Exception object among the Java comprises Exception Type and abnormal information, catch one unusual after, can carry out following processing:
(1) handling this dishes out unusually and not;
(2) do not handle and dish out former unusual;
(3) be packaged into and dish out once more after new unusual.
Packing is meant unusually and is set to new unusual " bait " unusually with original, and this packing technique allows senior unusual in user's jettison system, and does not lose original unusual detailed information.For the unusual situation of dishing out, JDK adopts the mode of unusual chain to handle, and just adds unusually in unusual chained list one by one, and all are dished out like this unusually just forms a unusual chain.
At above-mentioned error code administrative mechanism, the present invention also provides corresponding processing means embodiment.With reference to Fig. 3, be described multisystem error code management devices structured flowchart.Described device is arranged on the data conversion platform, be used for treatment conversion is carried out in the error message of service system and platform self generation, and then layering returns to different clients.Described device comprises that mainly service system fault processing unit 301, platform errors processing unit 302 and error code return unit 303.
Wherein, described service system fault processing unit 301 is mainly used in the analysis service system message, and judges whether comprise application error in the message according to the error identification in the message, if comprise, then extracts error message and adds in the global error structure.
Described platform errors processing unit 302 is used for the error identification according to platform inside, has judged whether the platform internal error, if having, then from the data processing of information of platform self and add in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of external error sign indicating number, convert described platform internal error to external error, and add in the described global error structure then.
Described error code returns unit 303 and is used for described application error, platform internal error and external error are formed message, returns to corresponding client.Preferably, because the message structure difference of different clients definition, need earlier various error messages to be mapped in the message structure of relative client definition so error code returns unit 303, and form message according to the order of service system mistake, platform external error, internal error and return.And owing to adopt the unusual nested mechanism of JDK, it is that interaction sequences layering according to different service systems and platform is returned that the error code of a plurality of service systems returns.
Preferably, described device also comprises format conversion unit 304, be used for calling according to described service system fault processing unit 301 and platform fault processing unit 302, convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.Like this, platform facilitates various misdatas is carried out unified management.
Based on above-mentioned error code management devices, the present invention also provides a kind of error code management system.With reference to Fig. 4, be the described error code management system of embodiment of the invention structure chart.Described system comprises data transaction platform 41, a plurality of service systems 42 that link to each other with this platform 41, and with the mutual different clients 43 of platform.The request that client 43 is initiated is transmitted to corresponding service system 42 via data transaction platform 41 and handles, and the return code (comprising error code) that service system 42 produces is transmitted to relative client 43 after also handling via data transaction platform 41.Wherein, the data exchange process between a plurality of service systems 42 also need be passed through data transaction platform 41 processing forward.
Described data transaction platform 41 comprises that service system fault processing unit 411, platform errors processing unit 412, error code return unit 413, and format conversion unit 414 is set preferably, the function that this plurality of units realizes can be not described in detail in this with reference to above-mentioned Fig. 3 explanation.
In the described error code management system, because treatment conversion has been carried out in 41 pairs of service systems 42 of data transaction platform and the platform 41 inner various error messages that produce, and carry out layering and handle, can layering show different error messages so return to the error code of client 43, for client user's debugging provides greatly convenient.
The part that does not describe in detail in Fig. 3, device shown in Figure 4, the system can be considered for length referring to the relevant portion of method shown in Figure 2, is not described in detail in this.
More than to a kind of multisystem error code management method provided by the present invention, Apparatus and system, be described in detail, used specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, part in specific embodiments and applications all can change.In sum, this description should not be construed as limitation of the present invention.
Claims (13)
1, a kind of multisystem error code management method is applied to the mutual of data transaction platform and a plurality of service systems, it is characterized in that, comprising:
The data transaction platform receives the service system message and resolves, if comprise error message, then adds in the global error structure;
According to the error identification of platform inside, judged whether the platform internal error, if having, then add in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Message is formed in error message in the described global error structure sent to client.
2, method according to claim 1, it is characterized in that, service system mistake and platform internal error are added to before the global error structure, also comprise: convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.
3, method according to claim 1, it is characterized in that, message is formed in error message also to be comprised before: according to the different definition of different clients to message structure, the error message in the global error structure is mapped in the message structure of relative client definition.
4, method according to claim 1 is characterized in that: described message is according to the der group bag of service system mistake, platform external error, platform internal error.
5, method according to claim 1 is characterized in that, also comprises: adopt the unusual nested mechanism of JDK, return error message according to the interaction sequences layering of different service systems and platform.
6, a kind of multisystem error code management devices is arranged on the data transaction platform, it is characterized in that, comprising:
Service system fault processing unit is used to receive service system message and parsing, if comprise error message, then adds in the global error structure;
The platform errors processing unit is used for the error identification according to platform inside, has judged whether the platform internal error, if having, then adds in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Error code returns the unit, is used for that message is formed in all error messages of described global error structure and sends to client.
7, device according to claim 6, it is characterized in that, also comprise: format conversion unit, be used for calling according to described service system fault processing unit and platform fault processing unit, convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.
8, device according to claim 6, it is characterized in that: described error code returns the unit earlier according to the different definition of different clients to message structure, error message in the global error structure is mapped in the message structure of relative client definition, and then forms the message transmission.
9, device according to claim 6 is characterized in that: described error code returns the unit and returns error message according to the order of service system mistake, platform external error, platform internal error.
10, device according to claim 6 is characterized in that: described error code returns the unit and adopts the unusual nested mechanism of JDK, returns error message according to the interaction sequences layering of different service systems and platform.
11, a kind of error code management system comprises data transaction platform and a plurality of service system, and with the mutual client of data transaction platform, it is characterized in that described data transaction platform comprises:
Service system fault processing unit is used to receive service system message and parsing, if comprise error message, then adds in the global error structure;
The platform errors processing unit is used for the error identification according to platform inside, has judged whether the platform internal error, if having, then adds in the described global error structure; According to the platform internal error sign indicating number that presets and the corresponding relation of platform external error sign indicating number, convert described platform internal error to platform external error, and add in the described global error structure then;
Error code returns the unit, is used for that message is formed in all error messages of described global error structure and sends to client.
12, system according to claim 11, it is characterized in that, described data transaction platform also comprises: format conversion unit, be used for calling according to described service system fault processing unit and platform fault processing unit, convert service system mistake and platform internal error to unified error format respectively, and then add in the global error structure.
13, system according to claim 11 is characterized in that: described error code returns the unit and returns error message according to the order of service system mistake, platform external error, platform internal error.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710307753.7A CN100574221C (en) | 2007-12-29 | 2007-12-29 | A kind of multisystem error code management method, Apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710307753.7A CN100574221C (en) | 2007-12-29 | 2007-12-29 | A kind of multisystem error code management method, Apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101197722A CN101197722A (en) | 2008-06-11 |
| CN100574221C true CN100574221C (en) | 2009-12-23 |
Family
ID=39547886
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710307753.7A Active CN100574221C (en) | 2007-12-29 | 2007-12-29 | A kind of multisystem error code management method, Apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100574221C (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101980176A (en) * | 2010-10-29 | 2011-02-23 | 华为数字技术有限公司 | Software error code transferring method, device and system |
| CN103297401A (en) * | 2012-03-01 | 2013-09-11 | 腾讯科技（深圳）有限公司 | Error code returning method and device |
| CN102891785B (en) * | 2012-09-18 | 2015-11-04 | 中兴通讯股份有限公司 | error code conversion method, system, PPPoE server and mobile terminal |
| CN104182683B (en) * | 2014-07-30 | 2017-10-13 | 中国工商银行股份有限公司 | A kind of monitoring method of online transaction, apparatus and system |
| CN104363072B (en) * | 2014-10-29 | 2019-08-13 | 中国建设银行股份有限公司 | A kind of error message transmitting escape methods, devices and systems |
| CN105590215B (en) * | 2015-10-29 | 2019-11-22 | 中国银联股份有限公司 | The Data Handling Equipment And Method of each inter-agency data error of online process |
| CN107172113B (en) * | 2016-03-08 | 2020-06-12 | 阿里巴巴集团控股有限公司 | Processing method and device in abnormal service call |
| CN107404456B (en) * | 2016-05-18 | 2020-05-05 | 阿里巴巴集团控股有限公司 | Error positioning method and device |
| CN106603520A (en) * | 2016-12-08 | 2017-04-26 | 深圳Tcl数字技术有限公司 | Abnormal information interception method and apparatus thereof |
| CN107038041B (en) * | 2016-12-27 | 2021-03-02 | 创新先进技术有限公司 | Data processing method, error code dynamic compatibility method, device and system |
| CN106874163B (en) * | 2016-12-29 | 2020-09-11 | 广州华多网络科技有限公司 | Method and system for displaying software error code information |
| CN107291605B (en) * | 2017-07-11 | 2020-09-22 | 苏州浪潮智能科技有限公司 | System log processing method and system |
| CN109460924A (en) * | 2018-11-14 | 2019-03-12 | 沈阳林科信息技术有限公司 | Mobile Internet equity products agency quotient's management system |
| CN111200654A (en) * | 2019-12-31 | 2020-05-26 | 中国银行股份有限公司 | Client request error processing method and device |
| CN112596494B (en) * | 2020-12-04 | 2023-02-10 | 中国航空工业集团公司成都飞机设计研究所 | Aircraft fault positioning method based on HMC code correlation analysis |
| CN113626247B (en) * | 2021-08-26 | 2024-03-22 | 宁波菊风系统软件有限公司 | Error code transmission method in distributed system |
| CN115955384A (en) * | 2022-12-16 | 2023-04-11 | 成都赛力斯科技有限公司 | Error code returning method, device and system |
-
2007
- 2007-12-29 CN CN200710307753.7A patent/CN100574221C/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101197722A (en) | 2008-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100574221C (en) | A kind of multisystem error code management method, Apparatus and system | |
| CN1187700C (en) | Fail-safe event driven transaction processing system and method | |
| CN1332538C (en) | Distributed on-line data communications system and method | |
| CN104272259B (en) | System and method for supporting the route based on version in transaction middleware machine environment | |
| CN103514565A (en) | Transaction abnormity processing unit of financial transaction processing system and method thereof | |
| CN102663649A (en) | Financial derivative transaction system | |
| CN103957188B (en) | A kind of enterprises service of symmetrical two-way decoupling describes method and service dispatch system | |
| NO311388B1 (en) | Implementation Independent Interface Specification System | |
| WO2021204044A1 (en) | Correction of blockchain data | |
| CN106027534A (en) | System for implementing financial message processing based on Netty | |
| CN104660435A (en) | Transactional network management engine for intelligent pipeline and network management transaction processing method of transactional network management engine | |
| CN111478827A (en) | Pressure testing method, device and system for block chain network | |
| JP2024506093A (en) | Cross-chain transaction processing methods and devices, electronic equipment and computer programs | |
| CN114240409A (en) | Cross-chain asset interaction method based on improved Hash time lock | |
| CN112991046A (en) | Electronic resource limit control method, device, equipment and storage medium | |
| CN110213071A (en) | Verification of data method, apparatus, system, computer equipment and storage medium | |
| CN113762912B (en) | Service processing method, equipment and storage medium of ABS service system | |
| US7131108B1 (en) | Software development system having particular adaptability to financial payment switches | |
| CN101925882A (en) | Method of improving replica server performance and replica server system | |
| Simborg et al. | Local area networks and the hospital | |
| CN108156061A (en) | Esb monitoring service platforms | |
| CN112053240A (en) | Method for realizing predictive speech machine function on block chain | |
| CN116991929A (en) | Micro-service system based on big hospital data | |
| CN110827172A (en) | Wisdom water affairs cloud service platform | |
| CN101620567A (en) | Error locating auxiliary method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |