CN114217932A - Third-party docking exception handling method and system - Google Patents
Third-party docking exception handling method and system Download PDFInfo
- Publication number
- CN114217932A CN114217932A CN202111600345.7A CN202111600345A CN114217932A CN 114217932 A CN114217932 A CN 114217932A CN 202111600345 A CN202111600345 A CN 202111600345A CN 114217932 A CN114217932 A CN 114217932A
- Authority
- CN
- China
- Prior art keywords
- docking
- party
- abnormal
- exception
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003032 molecular docking Methods 0.000 title claims abstract description 99
- 238000000034 method Methods 0.000 title claims abstract description 24
- 238000012545 processing Methods 0.000 claims abstract description 59
- 230000002159 abnormal effect Effects 0.000 claims abstract description 51
- 238000012423 maintenance Methods 0.000 claims description 12
- 230000005856 abnormality Effects 0.000 claims description 11
- 230000000977 initiatory effect Effects 0.000 claims description 8
- 238000011161 development Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/481—Exception handling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a third party docking exception handling method, which comprises the following steps: extracting the abnormal type and abnormal processing mode information of the service system, and inputting the information into the docking subsystem; the service system initiates a third party docking request and sends docking information to a Rabbitmq message queue; the docking subsystem consumes the docking information received in the Rabbitmq message queue, initiates a request to a third-party system according to the third-party address and the protocol type, and sends the docking information to a third party; the docking subsystem receives a service processing result returned by the third-party system, judges the result and carries out different processing according to whether the result is abnormal or not; the abnormal docking information is pushed to a service responsible person, so that manual intervention treatment is facilitated; the invention also discloses a third party docking exception handling system; the invention can ensure the smooth operation of the system service in the high concurrency scene and can realize the processing of the abnormal condition.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a third-party docking exception handling method and system.
Background
In the development process of a software system, with the popularity of micro-service concepts and designs, more and more services and scenes need to be interfaced with a third party, such as production information synchronization, inventory information synchronization, third party services and the like. Various abnormal conditions are often caused by reasons such as networks, programs and the like in the actual system docking process, so that the operation of the whole business process is influenced; in addition, in a high concurrency scenario, the conventional synchronization mode may affect the working efficiency of the original service, and greatly affect the normal development of the service.
The current means for handling the docking exception include increasing the timeout time and increasing the retry. Increasing the timeout time fails to solve the problem of abnormal interruption of the service; using retries directly can greatly increase system burden while impacting service efficiency.
Disclosure of Invention
The invention aims to provide a third-party docking exception handling method and system for solving the problems in the prior art, and the method and system are used for solving the problem of exception handling when a service system is docked with a third-party system in a high-concurrency scene, ensuring that the service of the system is smoothly carried out and increasing the fault tolerance of the system.
In order to achieve the purpose, the invention adopts the technical scheme that: a third party docking exception handling method comprises the following steps:
step 1, extracting the information of the abnormal type and the abnormal processing mode of a service system, and inputting the information into a docking subsystem;
step 2, the service system initiates a third party docking request and sends docking information to a Rabbitmq message queue;
step 3, receiving the docking information in the step 2 in a docking subsystem consumption Rabbitmq message queue, initiating a request to a third-party system according to a third-party address and a protocol type, and sending the docking information to a third party;
step 4, the docking subsystem receives a service processing result returned by the third-party system, judges the result and carries out different processing according to whether the result is abnormal or not;
and 5, pushing the abnormal docking information to a service responsible person, so that manual intervention is facilitated.
In a preferred embodiment, in step 1, the exception types include network connection timeout, data format exception and request status exception, and the exception handling manner includes automatic retry and manual handling.
As another preferred embodiment, in step 2, the docking information includes a message ID, a third party address, a protocol type, a docking service ID, and a request parameter.
As another preferred embodiment, in step 3, when a docking request is initiated to a third party, a try catch is used to perform all the parcels; and the method for consuming the Rabbitmq message by the docking subsystem adopts a manual signing mode.
As another preferred embodiment, in step 4, the performing exception handling on the docking subsystem includes the following steps:
A. if no abnormal information is returned, the butting is finished;
B. the program is abnormal, the type of the current abnormality is obtained, and an abnormality processing mode is searched according to the type of the abnormality;
C. the processing mode is automatically processed, whether the failure times exceed 3 times or not is judged, if not, the message is returned to the Rabbitmq queue for operation, the abnormity is recorded, and the abnormity times are increased; if the number of the messages exceeds 3 times, manually signing the Rabbitmq message, and storing abnormal information;
D. the processing mode is manual processing, and manual page is provided for manual retry according to the stored abnormal information.
The invention also provides a third party docking exception handling system, which comprises: the system comprises a business system, a docking subsystem and a third-party system; wherein:
the service system is used for service processing and initiating a third party docking request;
the third-party system is used for receiving the docking request and carrying out specific service processing;
the docking subsystem is used for uniformly scheduling and docking and analyzing and processing a docking result.
As a preferred embodiment, the docking subsystem includes an exception basic information maintenance module, an exception logic processing module, a docking module, an exception record tracing module and an exception manual maintenance module; wherein:
the abnormal basic information maintenance module is used for acquiring all abnormal types and abnormal processing modes of the service system;
the docking module is used for consuming a Rabbitmq message queue, receiving docking information of the service system, initiating a docking request to a third-party system and receiving a return result;
the exception logic processing module is used for analyzing the third-party service processing result and carrying out different logic processing according to different exception types and exception processing modes;
the abnormal system tracing module is used for storing the abnormal information analyzed and processed by the abnormal logic processing module and providing a query function for system tracing;
the exception manual maintenance module user manually processes the exception and the associated responsible person may continue to attempt to re-dock.
The invention has the beneficial effects that:
aiming at the abnormal situation of the third party in the butt joint, the invention can ensure the smooth operation of the system service under the high concurrency scene by introducing the Rabbitmq message queue and uniformly scheduling and processing the butt joint subsystem, and can realize the processing of the abnormal situation.
Drawings
Fig. 1 is a flowchart of a third party docking exception handling method in embodiment 1 of the present invention;
fig. 2 is a block diagram of a third-party docking exception handling system according to embodiment 2 of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Example 1
As shown in fig. 1, a third party docking exception handling method includes the following steps:
step 1: extracting the abnormal type and abnormal processing mode information of the service system, and inputting the information into the docking subsystem; the exception types comprise network connection timeout, data format exception, request state exception and the like, and the processing mode comprises automatic retry and manual processing;
step 2: the service system initiates a third party docking request and sends docking information to a Rabbitmq message queue; the docking information comprises a message ID, a third party address, a protocol type, a docking service ID, a request parameter and the like;
and step 3: and (3) the docking subsystem consumes the docking information in the Rabbitmq message queue in the step (2), initiates a request to a third-party system according to the third-party address and the protocol type, and sends the docking service ID and the request parameter to the third party. And when a docking request is sent to a third party, using try catch to wrap the whole package. Wherein, the method for receiving the subsystem consumption Rabbitmq message adopts a manual signing mode;
and 4, step 4: and the docking subsystem receives a service processing result returned by the third party, judges the result and carries out different processing according to whether the result is abnormal or not. The method for carrying out exception handling on the subsystem comprises the following steps:
a: if no abnormal information is returned, the butting is finished;
b: the program is abnormal, the type of the current abnormality is obtained, and an abnormality processing mode is searched according to the type of the abnormality;
c: the processing mode is automatically processed, whether the failure times exceed 3 times or not is judged, the message is returned to a Rabbitmq queue for operation, the abnormality is recorded, and the abnormality times are increased; if the number of the messages exceeds 3 times, manually signing the Rabbitmq message, and storing abnormal information;
d: the processing mode is manual processing, and a manual page is provided for manual retry according to the stored abnormal information;
and 5: and the abnormal information of system docking is pushed to a service responsible person, so that the manual intervention treatment is facilitated.
Example 2
As shown in fig. 2, a third-party docking exception handling system includes a service system, a docking subsystem, and a third-party system, where the docking subsystem includes an exception basic information maintenance module, an exception logic processing module, a docking module, an exception record tracing module, and an exception manual maintenance module.
The service system is used for service processing and initiating a third party docking request;
the third-party system is used for receiving the docking request and carrying out specific service processing;
the docking subsystem is used for uniformly scheduling docking and analyzing and processing a docking result; the basic abnormal information maintenance module is used for acquiring all abnormal types and abnormal processing modes of the service system; the docking module is used for consuming a Rabbitmq message queue, receiving docking information of the service system, initiating a docking request to a third-party system and receiving a return result; the exception logic processing module is used for analyzing the third-party service processing result and carrying out different logic processing according to different exception types and exception processing modes; the abnormal system tracing module stores the abnormal information analyzed and processed by the abnormal logic processing module by a user and provides a query function for system tracing; the exception human maintenance module user processes the exception manually, and the relevant responsible person can continue to try to re-dock.
The above-mentioned embodiments only express the specific embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention.
Claims (7)
1. A third party docking exception handling method is characterized by comprising the following steps:
step 1, extracting the information of the abnormal type and the abnormal processing mode of a service system, and inputting the information into a docking subsystem;
step 2, the service system initiates a third party docking request and sends docking information to a Rabbitmq message queue;
step 3, receiving the docking information in the step 2 in a docking subsystem consumption Rabbitmq message queue, initiating a request to a third-party system according to a third-party address and a protocol type, and sending the docking information to a third party;
step 4, the docking subsystem receives a service processing result returned by the third-party system, judges the result and carries out different processing according to whether the result is abnormal or not;
and 5, pushing the abnormal docking information to a service responsible person, so that manual intervention is facilitated.
2. The third-party docking exception handling method according to claim 1, wherein in step 1, the exception categories include network connection timeout, data format exception and request status exception, and the exception handling manner includes automatic retry and manual handling.
3. The third-party docking exception handling method according to claim 1, wherein in step 2, the docking information includes a message ID, a third-party address, a protocol type, a docking service ID, and a request parameter.
4. The third-party docking exception handling method according to claim 1, wherein in step 3, when a docking request is initiated to a third party, a try catch is used to perform all wrapping; and the method for consuming the Rabbitmq message by the docking subsystem adopts a manual signing mode.
5. The third-party docking exception handling method according to claim 1, wherein in step 4, the docking subsystem performs exception handling including the steps of:
A. if no abnormal information is returned, the butting is finished;
B. the program is abnormal, the type of the current abnormality is obtained, and an abnormality processing mode is searched according to the type of the abnormality;
C. the processing mode is automatically processed, whether the failure times exceed 3 times or not is judged, if not, the message is returned to the Rabbitmq queue for operation, the abnormity is recorded, and the abnormity times are increased; if the number of the messages exceeds 3 times, manually signing the Rabbitmq message, and storing abnormal information;
D. the processing mode is manual processing, and manual page is provided for manual retry according to the stored abnormal information.
6. A third party docking exception handling system, comprising: the system comprises a business system, a docking subsystem and a third-party system; wherein:
the service system is used for service processing and initiating a third party docking request;
the third-party system is used for receiving the docking request and carrying out specific service processing;
the docking subsystem is used for uniformly scheduling and docking and analyzing and processing a docking result.
7. The third-party docking exception handling system according to claim 6, wherein the docking subsystem comprises an exception basic information maintenance module, an exception logic processing module, a docking module, an exception record tracing module and an exception manual maintenance module; wherein:
the abnormal basic information maintenance module is used for acquiring all abnormal types and abnormal processing modes of the service system;
the docking module is used for consuming a Rabbitmq message queue, receiving docking information of the service system, initiating a docking request to a third-party system and receiving a return result;
the exception logic processing module is used for analyzing the third-party service processing result and carrying out different logic processing according to different exception types and exception processing modes;
the abnormal system tracing module is used for storing the abnormal information analyzed and processed by the abnormal logic processing module and providing a query function for system tracing;
the exception manual maintenance module user manually processes the exception and the associated responsible person may continue to attempt to re-dock.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111600345.7A CN114217932A (en) | 2021-12-24 | 2021-12-24 | Third-party docking exception handling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111600345.7A CN114217932A (en) | 2021-12-24 | 2021-12-24 | Third-party docking exception handling method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114217932A true CN114217932A (en) | 2022-03-22 |
Family
ID=80705723
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111600345.7A Pending CN114217932A (en) | 2021-12-24 | 2021-12-24 | Third-party docking exception handling method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114217932A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114553932A (en) * | 2022-04-24 | 2022-05-27 | 深圳市明源云科技有限公司 | System integration docking method, device, equipment and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160350170A1 (en) * | 2014-05-30 | 2016-12-01 | Apteligent, Inc. | System for Monitoring and Tracking Application Crashes Occurring on Different Mobile Devices |
| US20180324118A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | Messaging queue service api optimization system |
| CN110647416A (en) * | 2019-08-30 | 2020-01-03 | 福建天泉教育科技有限公司 | Message queue tracking and recording method and system |
| CN111899105A (en) * | 2020-08-04 | 2020-11-06 | 深圳乐信软件技术有限公司 | System exception handling method and device, computer equipment and storage medium |
| CN112463407A (en) * | 2020-11-25 | 2021-03-09 | 北京神州数字科技有限公司 | Message transmission and consumption method |
| CN112948174A (en) * | 2021-02-03 | 2021-06-11 | 江苏苏宁物流有限公司 | Message processing method and device, computer equipment and storage medium |
-
2021
- 2021-12-24 CN CN202111600345.7A patent/CN114217932A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160350170A1 (en) * | 2014-05-30 | 2016-12-01 | Apteligent, Inc. | System for Monitoring and Tracking Application Crashes Occurring on Different Mobile Devices |
| US20180324118A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | Messaging queue service api optimization system |
| CN110647416A (en) * | 2019-08-30 | 2020-01-03 | 福建天泉教育科技有限公司 | Message queue tracking and recording method and system |
| CN111899105A (en) * | 2020-08-04 | 2020-11-06 | 深圳乐信软件技术有限公司 | System exception handling method and device, computer equipment and storage medium |
| CN112463407A (en) * | 2020-11-25 | 2021-03-09 | 北京神州数字科技有限公司 | Message transmission and consumption method |
| CN112948174A (en) * | 2021-02-03 | 2021-06-11 | 江苏苏宁物流有限公司 | Message processing method and device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114553932A (en) * | 2022-04-24 | 2022-05-27 | 深圳市明源云科技有限公司 | System integration docking method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9967315B2 (en) | Electronic device, storage medium and file transferring method | |
| US8478895B2 (en) | Content adaptation realizing method and content adaptation server | |
| US20070158404A1 (en) | Method and system for management of terminal devices | |
| CN102546135B (en) | Active/standby server switched system and method | |
| EP3258653A1 (en) | Message pushing method and device | |
| CN110650164B (en) | File uploading method and device, terminal and computer storage medium | |
| CN108833443B (en) | Message transmission method and system and computer equipment | |
| CN111526181B (en) | Data request processing method and system and computing device | |
| CN114217932A (en) | Third-party docking exception handling method and system | |
| US20220182305A1 (en) | Request Processing System and Method Thereof | |
| CN104821889B (en) | A kind of processing method and equipment of backup message | |
| CN101610402A (en) | Video recording interrupts the method and system of recovery in a kind of video monitoring process | |
| CN107105037B (en) | Distributed video CDN resource management system and method based on file verification | |
| WO2023125777A1 (en) | Video recording data replenishment method, cloud storage server, system and storage medium | |
| CN114390452B (en) | Message sending method and related equipment | |
| CN115866535A (en) | Method and system for realizing 5G message access by multiple protocols | |
| CN114048467A (en) | Model data processing method, device, equipment and storage medium based on intrusion detection system | |
| CN112333262A (en) | Data updating prompting method and device, computer equipment and readable storage medium | |
| CN112667393A (en) | Method and device for building distributed task computing scheduling framework and computer equipment | |
| CN101674568A (en) | Integrated service management platform and service subscription method thereof | |
| CN113411828A (en) | Method, device and equipment for sensing call quality and computer readable storage medium | |
| CN110896413A (en) | Message processing method and device | |
| CN112751834B (en) | Https-based bidirectional authentication and accounting method, system and computer equipment | |
| CN114172674B (en) | Abnormal data detection method, device, equipment and computer medium | |
| CN113315875B (en) | Call information synchronization method and device, call information synchronization equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |