Dead message queue transaction message processing method, device and equipment, medium and product

Abstract

The embodiment of the invention provides a transaction message processing method and device for a dead message queue, equipment, a medium and a product. The method can be used in financial or other fields. The method comprises the following steps: acquiring a dead message queue; monitoring the dead message queue to identify a transaction message entering the dead message queue; acquiring data information of the transaction message; storing the data information of the transaction message to a transaction message data table; generating an operation interface according to the transaction message data table; and in response to an operation of a user on the operation interface, performing message processing on the transaction message. The method is used for achieving the effect of improving the timeliness and efficiency of transaction message processing of the dead message queue.

Description

Technical Field

[0001] The present application relates to the financial field or other fields, and in particular to a transaction message processing method, device, equipment, medium and product for a dead letter queue. Background Art

[0002] Generally speaking, producers deliver messages (transaction messages) to queues, and consumers take messages from queues for consumption. However, sometimes some messages in the queue cannot be consumed due to specific reasons. If such messages are not processed later, they become dead letters. All dead letters will be placed in the dead letter queue.

[0003] In order to prevent transaction messages from being lost in the dead letter queue, the traditional method is for maintenance personnel to manually monitor the depth of the dead letter queue through scripts. If manual monitoring finds that there are transaction messages in the dead letter queue, the message queue (MQ) tool is used to retrieve the message and then manually send it to developers and business personnel. After manual identification, if there are transactions that need to be resent, the MQ tool is used to manually send them.

[0004] However, the existing technology cannot efficiently and comprehensively process transaction messages in the dead letter queue, and the timeliness and efficiency of transaction message processing in the dead letter queue are poor. Summary of the invention

[0005] The present application provides a transaction message processing method, device, equipment, medium and product for a dead letter queue, so as to achieve the effect of improving the timeliness and efficiency of transaction message processing for a dead letter queue.

[0006] In a first aspect, the present application provides a transaction message processing method of a dead letter queue, comprising:

[0007] Get the dead letter queue;

[0008] Monitoring the dead letter queue to identify transaction messages entering the dead letter queue;

[0009] Obtaining data information of the transaction message;

[0010] Saving the data information of the transaction message to the transaction message data table;

[0011] Generate an operation interface according to the transaction message data table;

[0012] In response to the user's operation on the operation interface, the transaction message is processed.

[0013] Here, the present application provides a method for automatically processing transaction messages in a dead letter queue. For any dead letter queue, the method monitors in real time whether there are transaction messages entering the dead letter queue, reads the data information of the transaction messages entering the dead letter queue, and saves the data information of the transaction messages in a pre-designed transaction message data table, thereby realizing the monitoring of all transaction messages in the dead letter queue. Based on the transaction message data table, an operation interface for user operation can be generated to process the transaction messages according to the user's operation, without the need for manual maintenance, monitoring and sending of transaction messages. Automated and real-time monitoring and recording can quickly capture transaction messages in the dead letter queue. The automatically generated operation interface also provides users with an efficient and visual message processing method, thereby improving the timeliness and efficiency of transaction message processing in the dead letter queue.

[0014] Optionally, generating an operation interface according to the transaction message data table includes:

[0015] Generate a query interface according to the transaction message data table;

[0016] In response to a query operation of a user on the query interface, determining a transaction message corresponding to the query operation;

[0017] An operation interface is generated according to the transaction message corresponding to the query operation.

[0018] Among them, the present application provides a query interface for users, and a query interface can be generated based on the transaction message data table. Users can initiate selection or input operations on the query interface in a targeted manner, and can intuitively provide users with an efficient interactive interface, so that users can timely understand the transaction messages in the dead letter queue, and provide users with transaction progress in a timely manner, further improving the timeliness and efficiency of transaction message processing in the dead letter queue, and improving user experience.

[0019] Optionally, generating an operation interface according to the transaction message corresponding to the query operation includes:

[0020] Generate a query result display interface according to the transaction message corresponding to the query operation;

[0021] In response to a selection operation by a user on the query interface display interface, determining a transaction message corresponding to the selection operation;

[0022] An operation interface is generated according to the transaction message corresponding to the selection operation.

[0023] Among them, after the user initiates a query operation, the present application can generate a query result display interface according to the transaction message corresponding to the query operation, thereby intuitively displaying the query results to the user, improving the query efficiency of the transaction message in the dead letter queue. At the same time, the user can initiate a selection operation on the query result display interface, select the transaction message that needs to be controlled, and quickly locate the transaction message that needs to be operated, further improving the timeliness and efficiency of the transaction message processing in the dead letter queue and improving the user experience.

[0024] Optionally, the performing message processing on the transaction message in response to an operation of the user on the operation interface includes:

[0025] In response to a processing operation of the user on the operation interface, determining a processing method for the transaction message corresponding to the selection operation, wherein the processing method includes discarding and resending;

[0026] According to the processing method, the transaction message corresponding to the selection operation is discarded or resent.

[0027] Here, the present application can determine the user's processing method for the transaction message based on the processing operation initiated by the user on the operation interface, and quickly implement the processing of the transaction message.

[0028] Optionally, the discarding or resending of the transaction message corresponding to the selection operation according to the processing mode includes:

[0029] If the processing method is resending processing, the transaction message corresponding to the selection operation is added to the normal queue of the message center, so as to resend the transaction message corresponding to the selection operation through the normal queue;

[0030] If the processing method is discard processing, the transaction message corresponding to the selection operation is deleted from the dead letter queue.

[0031] Here, the present application can quickly execute the disposal or retransmission processing of the transaction message based on the user's operation, thereby improving the timeliness and efficiency of the transaction message processing, and reducing the space occupied by the dead letter queue through the disposal processing.

[0032] Optionally, the data information includes multiple of the transaction serial number, the time when the message enters the dead letter queue, the message number, the message type, the message status, the message source system name, the message source system identity number, the dead letter queue name, the normal queue name and the message details.

[0033] Based on the above data, transaction messages can be accurately identified and diversified transaction message data information can be displayed to users, thereby improving the accuracy of transaction message processing in the dead letter queue and improving user experience.

[0034] In a second aspect, the present application provides a transaction message processing device for a dead letter queue, comprising:

[0035] The first acquisition module is used to obtain the dead letter queue;

[0036] A monitoring module, used for monitoring the dead letter queue to identify transaction messages entering the dead letter queue;

[0037] A second acquisition module, used to acquire data information of the transaction message;

[0038] A saving module, used for saving the data information of the transaction message to a transaction message data table;

[0039] A generating module, used for generating an operation interface according to the transaction message data table;

[0040] The processing module is used to process the transaction message in response to the user's operation on the operation interface.

[0041] Optionally, the generating module specifically includes:

[0042] A first sub-generation module, used to generate a query interface according to the transaction message data table;

[0043] A first sub-determining module, configured to determine a transaction message corresponding to a query operation performed by a user on the query interface;

[0044] The second sub-generation module is used to generate an operation interface according to the transaction message corresponding to the query operation.

[0045] Optionally, the second sub-generation module is specifically used to:

[0046] Generate a query result display interface according to the transaction message corresponding to the query operation;

[0047] In response to a selection operation by a user on the query interface display interface, determining a transaction message corresponding to the selection operation;

[0048] An operation interface is generated according to the transaction message corresponding to the selection operation.

[0049] Optionally, the processing module is specifically used for:

[0050] In response to a processing operation of the user on the operation interface, determining a processing method for the transaction message corresponding to the selection operation, wherein the processing method includes discarding and resending;

[0051] According to the processing method, the transaction message corresponding to the selection operation is discarded or resent.

[0052] Optionally, the processing module is further specifically configured to:

[0053] If the processing method is resending processing, the transaction message corresponding to the selection operation is added to the normal queue of the message center, so as to resend the transaction message corresponding to the selection operation through the normal queue;

[0054] If the processing method is discard processing, the transaction message corresponding to the selection operation is deleted from the dead letter queue.

[0055] Optionally, the data information includes multiple of the transaction serial number, the time when the message enters the dead letter queue, the message number, the message type, the message status, the message source system name, the message source system identity number, the dead letter queue name, the normal queue name and the message details.

[0056] In a third aspect, the present application provides a transaction message processing device for a dead letter queue, comprising: a memory, a processor;

[0057] The memory stores computer-executable instructions;

[0058] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0059] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the above first aspect and / or various possible implementations of the first aspect.

[0060] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementations of the first aspect.

[0061] The transaction message processing method, device, equipment, medium and product for the dead letter queue provided in the present application monitor in real time whether there is a transaction message entering the dead letter queue for any dead letter queue, read the data information of the transaction message entering the dead letter queue, and save the data information of the transaction message into a pre-designed transaction message data table, thereby realizing the monitoring of all transaction messages in the dead letter queue. Based on the transaction message data table, an operation interface for user operation can be generated to process the transaction message according to the user's operation, without the need for manual maintenance, monitoring and sending of transaction messages. Automated and real-time monitoring and recording can quickly capture transaction messages in the dead letter queue. The automatically generated operation interface also provides users with an efficient and visual message processing method, thereby improving the timeliness and efficiency of transaction message processing in the dead letter queue. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0063] Figure 1 A schematic diagram of a transaction message processing system architecture of a dead letter queue provided in an embodiment of the present application;

[0064] Figure 2 A flowchart of a transaction message processing method for a dead letter queue provided in an embodiment of the present application;

[0065] Figure 3 A schematic diagram of a transaction message data table provided in an embodiment of the present application;

[0066] Figure 4 An interface design intention of a query interface provided in an embodiment of the present application;

[0067] Figure 5 The interface design intention of a query result display interface provided in an embodiment of the present application;

[0068] Figure 6 An interface design intention of an operation interface provided in an embodiment of the present application;

[0069] Figure 7 A schematic diagram of the message flow of a dead letter queue transaction message re-entry mechanism provided in an embodiment of the present application;

[0070] Figure 8 A schematic diagram of the structure of a transaction message processing device for a dead letter queue provided in an embodiment of the present application;

[0071] Fig. 9 A schematic diagram of the structure of a transaction message processing device for a dead letter queue provided in an embodiment of the present application.

[0072] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0073] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0074] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0075] It should be noted that the transaction message processing method, device, equipment, medium and product of the dead letter queue of the present application can be used in the financial field or other fields, and can also be used in any field other than the financial field or other fields. The application field of the transaction message processing method, device, equipment, medium and product of the dead letter queue of the present application is not limited.

[0076] The specific application scenarios of this application are scenarios for transaction clearing, payment settlement, or scenarios such as user consumption and stored-value activities. The embodiments of this application are applicable to any transaction scenarios.

[0077] First, the terms involved in this application are explained:

[0078] Dead letter queue: In the message queue, it is a special queue used to store messages that cannot be processed normally.

[0079] When a transaction processing system (such as a clearing system) processes global local clearing and remittance business, due to various reasons such as network jitter and high system pressure, remittance transaction messages occasionally enter the MQ dead letter queue. In this scenario, the transaction processing system cannot perceive the transaction message and the remittance cannot be completed. How to efficiently monitor the transaction messages in the dead letter queue and resend them is a problem that needs to be solved. In order to prevent the transaction message from being lost in the dead letter queue, the traditional method is for the maintenance personnel to monitor the depth of the dead letter queue through scripts. If there is a transaction message in the dead letter queue, the MQ tool is used to take out the message and then manually send it to the developer and business personnel. After manual identification, if there is a transaction that needs to be resent, the MQ tool is used to manually send it. The above traditional solutions rely heavily on manual identification by the development, operation and maintenance, and business personnel, with poor timeliness and low efficiency, and a long operation and maintenance approval process is required. The existing technology cannot efficiently and comprehensively process the transaction messages in the dead letter queue, and the timeliness and efficiency of the transaction message processing in the dead letter queue are poor.

[0080] The method for processing transaction messages in a dead letter queue provided in the present application is intended to solve the above technical problems in the prior art.

[0081] In order to solve the above problems, the embodiments of the present application provide a transaction message processing method, device, equipment, medium and product for a dead letter queue, wherein the method can monitor the transaction messages in the dead letter queue in real time, save the transaction messages to the transaction message data table, display the operation interface to the user, and perform operations on the transaction messages in the dead letter queue according to the user's operations.

[0082] Optionally, the embodiment of the present application can read the transaction messages in the MQ dead letter queue in real time.

[0083] Optionally, the embodiment of the present application designs a data table for reading messages and saving them to a database.

[0084] Optionally, the embodiment of the present application designs a web page, and business personnel can query the transaction messages that enter the dead letter queue.

[0085] Optionally, the embodiment of the present application designs a WEB page, and business personnel can resend the message to a normal MQ receiving queue.

[0086] Optional, Figure 1 A schematic diagram of a dead letter queue transaction message processing system architecture provided in an embodiment of the present application. Figure 1 In the above architecture, the above architecture includes at least one of a data acquisition device 101, a processing device 102 and a display device 103.

[0087] It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the architecture of the transaction message processing system of the dead letter queue. In other feasible implementations of the present application, the above architecture may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently, which can be determined according to the actual application scenario and is not limited here. Figure 1 The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0088] In a specific implementation process, the data acquisition device 101 may include an input / output interface and may also include a communication interface. The data acquisition device 101 may be connected to the processing device via the input / output interface or the communication interface.

[0089] The processing device 102 can monitor the transaction messages in the dead letter queue in real time, save the transaction messages to the transaction message data table, display the operation interface to the user, and perform operations on the transaction messages in the dead letter queue according to the user's operations.

[0090] The display device 103 may also be a touch display screen or a screen of a terminal device, which is used to receive user instructions while displaying the above content to achieve interaction with the user.

[0091] It should be understood that the above-mentioned processing device can be implemented by a processor reading instructions in a memory and executing the instructions, or it can be implemented by a chip circuit.

[0092] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0093] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0094] Optionally, Figure 2 A flowchart of a transaction message processing method for a dead letter queue provided in an embodiment of the present application. The execution subject of the embodiment of the present application can be Figure 1 The specific execution subject can be determined according to the actual application scenario. Figure 2 As shown, the method comprises the following steps:

[0095] S201: Get the dead letter queue.

[0096] Optionally, one dead letter queue or multiple dead letter queues may be obtained. The embodiment of the present application may process transaction messages for a single dead letter queue, or may process transaction messages of multiple dead letter queues in batches.

[0097] S202: Monitor the dead letter queue to identify the transaction message entering the dead letter queue.

[0098] Optionally, the embodiment of the present application monitors the dead letter queue in real time to identify the message entering the dead letter queue, where the message refers to the transaction message.

[0099] S203: Obtain data information of the transaction message.

[0100] Optionally, the data information includes multiple of the transaction serial number, the time when the message enters the dead letter queue, the message number, the message type, the message status, the message source system name, the message source system identity document (ID), the dead letter queue name, the normal queue name and the message details.

[0101] S204: Save the data information of the transaction message to the transaction message data table.

[0102] Optionally, if a message is identified as incoming, it is read and saved in a data table.

[0103] In one possible implementation, Figure 3 A schematic diagram of a transaction message data table provided in an embodiment of the present application. For a transaction message, Figure 3 The form shown is stored in the transaction message data table. One transaction message data table can store data information of multiple transaction messages. It can be understood that Figure 3 This is merely illustrative. In a specific implementation, the transaction message data table may have more or fewer entries, and the embodiments of the present application do not impose any specific limitation on this.

[0104] S205: Generate an operation interface according to the transaction message data table.

[0105] S206: In response to the user's operation on the operation interface, the transaction message is processed.

[0106] Here, an embodiment of the present application provides a method for automatically processing transaction messages in a dead letter queue. For any dead letter queue, the method monitors in real time whether there are transaction messages entering the dead letter queue, reads the data information of the transaction messages entering the dead letter queue, and saves the data information of the transaction messages in a pre-designed transaction message data table, thereby realizing the monitoring of all transaction messages in the dead letter queue. Based on the transaction message data table, an operation interface for user operation can be generated to process the transaction messages according to the user's operation, without the need for manual maintenance, monitoring and sending of transaction messages. Automated and real-time monitoring and recording can quickly capture transaction messages in the dead letter queue. The automatically generated operation interface also provides users with an efficient and visual message processing method, thereby improving the timeliness and efficiency of transaction message processing in the dead letter queue.

[0107] Step S205 and step S206 are explained in detail below:

[0108] Optionally, the transaction message processing system of the dead letter queue of the embodiment of the present application may include a module for querying and retransmitting dead letter queue transaction messages, which module provides a set of pages, wherein in the query page, business personnel can query the detailed information of the transaction messages in the dead letter queue in real time, including the time when the message entered the queue, the detailed content of the message, where the message came from, where the message should go, etc.; in the retransmission page, business personnel can choose to resend or directly discard the message for a specific transaction message.

[0109] Optionally, an operation interface is generated according to the transaction message data table, including:

[0110] A query interface is generated according to the transaction message data table; in response to a query operation of a user on the query interface, a transaction message corresponding to the query operation is determined; and an operation interface is generated according to the transaction message corresponding to the query operation.

[0111] Optionally, the query operation may be an input and / or selection operation of the user on the query interface, specifically, an operation such as clicking or double-clicking.

[0112] Optionally, the query interface is generated based on a header of the transaction message data table, or based on data information corresponding to each header of the transaction message data table.

[0113] In some possible implementations, Figure 4 The interface design intention of a query interface provided in the embodiment of the present application is as follows: Figure 4 As shown in the figure, the query interface displays the header of the transaction message data table (type of each data information), and the user can enter the content to be queried through the input box and / or selection box corresponding to the header of the transaction message data table. Figure 4In the dead letter queue transaction message query page, a query condition combination is provided. Users can enter multiple or one query condition to perform the query. It is understandable that Figure 4 This is merely an illustration, and the embodiments of the present application do not impose any specific restrictions on the display format of the query interface.

[0114] Among them, the embodiment of the present application provides a query interface for users. A query interface can be generated based on the transaction message data table. Users can initiate selection or input operations on the query interface in a targeted manner, which can intuitively provide users with an efficient interactive interface, facilitate users to timely understand the transaction messages in the dead letter queue, and provide users with transaction progress in a timely manner, further improving the timeliness and efficiency of transaction message processing in the dead letter queue, and improving user experience.

[0115] Optionally, an operation interface is generated according to a transaction message corresponding to the query operation, including:

[0116] Generate a query result display interface based on the transaction message corresponding to the query operation; determine the transaction message corresponding to the selection operation in response to the user's selection operation on the query display interface; generate an operation interface based on the transaction message corresponding to the selection operation.

[0117] Optionally, the query operation may correspond to one or more transaction messages, and accordingly, the query result display interface may also simultaneously display data information of one or more transaction messages.

[0118] Optionally, the selection operation may be an input and / or selection operation of the user on the query interface, specifically, an operation such as clicking or double-clicking.

[0119] In some possible implementations, Figure 5 The interface design intention of a query result display interface provided in the embodiment of the present application is as follows: Figure 5 As shown, the query interface displays data information of multiple transaction messages and provides a detail button for the user to click. The user clicks the detail button to trigger the operation interface.

[0120] In some possible implementations, Figure 6 The interface design intention of an operation interface provided in the embodiment of the present application is as follows: Figure 6 As shown, the operation interface displays data information of the transaction message to be operated, and provides return, cancel and resend buttons for users to click. When the user clicks the button, the corresponding operation can be triggered.

[0121] Optionally, the operation interface may correspond to a transaction message, that is, the user Figure 5A selected transaction message is processed for a transaction message. Optionally, the operation interface may correspond to multiple transaction messages, and the user may select to process multiple transaction messages in batches on the query interface to improve the processing efficiency of the transaction messages.

[0122] Understandably, Figure 5 and Figure 6 This is for illustration only, and the embodiments of the present application do not impose any specific restrictions on the display format of any interface.

[0123] Among them, the embodiment of the present application can generate a query result display interface according to the transaction message corresponding to the query operation after the user initiates a query operation, so as to intuitively display the query results to the user, thereby improving the query efficiency of the transaction message in the dead letter queue. At the same time, the user can initiate a selection operation on the query result display interface, select the transaction message that needs to be controlled, and quickly locate the transaction message that needs to be operated, thereby further improving the timeliness and efficiency of the transaction message processing in the dead letter queue and improving the user experience.

[0124] Optionally, in response to an operation of the user on the operation interface, message processing is performed on the transaction message, including:

[0125] In response to a processing operation performed by a user on the operation interface, determining a processing method for a transaction message corresponding to the selected operation, wherein the processing method includes discarding and resending;

[0126] According to the processing method, the transaction message corresponding to the selected operation is discarded or resent.

[0127] Here, the embodiment of the present application can determine the user's processing method for the transaction message based on the processing operation initiated by the user on the operation interface, and quickly implement the processing of the transaction message.

[0128] Optionally, according to the processing mode, the transaction message corresponding to the selection operation is discarded or resent, including:

[0129] If the processing method is resending, the transaction message corresponding to the selected operation is added to the normal queue of the message center, so that the transaction message corresponding to the selected operation is resent through the normal queue;

[0130] If the processing method is to discard, the transaction message corresponding to the selection operation will be deleted from the dead letter queue.

[0131] Here, the embodiment of the present application can quickly execute the disposal or retransmission processing of the transaction message based on the user's operation, thereby improving the timeliness and efficiency of the transaction message processing, and reducing the space occupied by the dead letter queue through the disposal processing.

[0132] In some possible implementations, based on the transaction message processing method of the dead letter queue provided in the embodiment of the present application, Figure 7 A schematic diagram of the message flow of a dead letter queue transaction message re-entry mechanism provided in an embodiment of the present application, such as Figure 7 As shown, the embodiment of the present application is based on the financial message transmission (SWIFT) network and the system for processing transactions, and realizes efficient processing of all transaction messages, especially messages in the dead letter queue. The specific process is as follows: 1. The transaction message enters the normal receiving queue of the message center of the system for processing transactions from the SWIFT network; 2. The system for processing transactions performs business processing 3. If the system for processing transactions completes the normal processing, the process ends; 4. If the system for processing transactions cannot process normally due to various reasons, the message enters the dead letter queue of the system for processing transactions; 5. The program monitors the dead letter queue of the system for processing transactions in real time; 6. If it is monitored that a transaction message enters the dead letter queue, it is saved in the data table; 7. The business personnel query the transaction message entering the dead letter queue; 8. The business personnel selects the operation to resend the transaction message. It does not rely on development and operation and maintenance personnel. Only business personnel can efficiently complete the monitoring of the dead letter queue transaction message and resend it. Good timeliness and high efficiency.

[0133] Figure 8 A structural diagram of a transaction message processing device for a dead letter queue provided in an embodiment of the present application, such as Figure 8 As shown, the transaction message processing device of the dead letter queue provided in this embodiment includes a first acquisition module 801, a monitoring module 802, a second acquisition module 803, a storage module 804, a generation module 805 and a processing module 806. The transaction message processing device of the dead letter queue here can be the above-mentioned processing device, the processor itself, or a chip or integrated circuit that implements the function of the processor. It should be noted here that the division of the first acquisition module 801, the monitoring module 802, the second acquisition module 803, the storage module 804, the generation module 805 and the processing module 806 is only a division of logical functions, and the two can be physically integrated or independent.

[0134] Wherein, the first acquisition module is used to obtain the dead letter queue;

[0135] A monitoring module is used to monitor the dead letter queue to identify transaction messages entering the dead letter queue;

[0136] The second acquisition module is used to acquire data information of the transaction message;

[0137] A saving module, used to save the data information of the transaction message to the transaction message data table;

[0138] A generation module is used to generate an operation interface according to the transaction message data table;

[0139] The processing module is used to process the transaction message in response to the user's operation on the operation interface.

[0140] Optionally, the generation module specifically includes:

[0141] The first sub-generation module is used to generate a query interface according to the transaction message data table;

[0142] A first sub-determining module, configured to determine, in response to a query operation performed by a user on a query interface, a transaction message corresponding to the query operation;

[0143] The second sub-generation module is used to generate an operation interface according to the transaction message corresponding to the query operation.

[0144] Optionally, the second sub-generation module is specifically used for:

[0145] Generate a query result display interface based on the transaction message corresponding to the query operation;

[0146] In response to a selection operation of a user on a query interface display interface, determining a transaction message corresponding to the selection operation;

[0147] Generate an operation interface based on the transaction message corresponding to the selected operation.

[0148] Optionally, the processing module is specifically used for:

[0149] In response to a processing operation performed by a user on the operation interface, determining a processing method for a transaction message corresponding to the selected operation, wherein the processing method includes discarding and resending;

[0150] According to the processing method, the transaction message corresponding to the selected operation is discarded or resent.

[0151] Optionally, the processing module is further specifically configured to:

[0152] If the processing method is resending, the transaction message corresponding to the selected operation is added to the normal queue of the message center, so that the transaction message corresponding to the selected operation is resent through the normal queue;

[0153] If the processing method is to discard, the transaction message corresponding to the selection operation will be deleted from the dead letter queue.

[0154] Optionally, the data information includes multiple of the transaction serial number, the time when the message enters the dead letter queue, the message number, the message type, the message status, the message source system name, the message source system identification number, the dead letter queue name, the normal queue name and the message details.

[0155] refer to Fig. 9, which shows a schematic diagram of the structure of a transaction message processing device 900 suitable for implementing a dead letter queue of an embodiment of the present disclosure, and the transaction message processing device 900 of the dead letter queue can be a terminal device or a server. The terminal device can include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (PMPs), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The transaction message processing device of the dead letter queue shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0156] like Fig. 9 As shown, the transaction message processing device 900 of the dead letter queue may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 to a random access memory (RAM) 903. Various programs and data required for the operation of the transaction message processing device 900 of the dead letter queue are also stored in the RAM 903. The processing device 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0157] Typically, the following devices may be connected to the I / O interface 905: input devices 906 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 907 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 908 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 909. The communication device 909 may allow the transaction message processing device 900 of the dead letter queue to communicate with other devices wirelessly or by wire to exchange data. Although Fig. 9 The transaction message processing device 900 of the dead letter queue having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0158] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 909, or installed from a storage device 908, or installed from a ROM 902. When the computer program is executed by the processing device 901, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0159] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0160] The computer-readable medium may be included in the transaction message processing device of the dead letter queue; or may exist independently without being assembled into the transaction message processing device of the dead letter queue.

[0161] The computer-readable medium carries one or more programs. When the one or more programs are executed by the transaction message processing device of the dead letter queue, the transaction message processing device of the dead letter queue executes the method shown in the above embodiment.

[0162] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0163] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0164] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0165] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0166] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0167] The transaction message processing device of the dead letter queue in the embodiment of the present application can be used to execute the technical solutions in the above-mentioned method embodiments of the present application. Its implementation principles and technical effects are similar and will not be repeated here.

[0168] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement any of the above-mentioned transaction message processing methods for a dead letter queue.

[0169] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement any of the above-mentioned transaction message processing methods for a dead letter queue.

[0170] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A transaction message processing method for a dead letter queue, characterized in that: include: Get the dead letter queue; Monitoring the dead letter queue to identify transaction messages entering the dead letter queue; Obtaining data information of the transaction message; Saving the data information of the transaction message to the transaction message data table; Generate an operation interface according to the transaction message data table; In response to the user's operation on the operation interface, the transaction message is processed.

2. The method according to claim 1, characterized in that: The step of generating an operation interface according to the transaction message data table includes: Generate a query interface according to the transaction message data table; In response to a query operation of a user on the query interface, determining a transaction message corresponding to the query operation; An operation interface is generated according to the transaction message corresponding to the query operation.

3. The method according to claim 2, characterized in that The step of generating an operation interface according to the transaction message corresponding to the query operation includes: Generate a query result display interface according to the transaction message corresponding to the query operation; In response to a selection operation by a user on the query interface display interface, determining a transaction message corresponding to the selection operation; An operation interface is generated according to the transaction message corresponding to the selection operation.

4. The method according to claim 3, characterized in that The processing of the transaction message in response to the user's operation on the operation interface includes: In response to a processing operation of the user on the operation interface, determining a processing method for the transaction message corresponding to the selection operation, wherein the processing method includes discarding and resending; According to the processing method, the transaction message corresponding to the selection operation is discarded or resent.

5. The method according to claim 4, characterized in that According to the processing mode, the transaction message corresponding to the selection operation is discarded or resent, including: If the processing method is resending processing, the transaction message corresponding to the selection operation is added to the normal queue of the message center, so as to resend the transaction message corresponding to the selection operation through the normal queue; If the processing method is discard processing, the transaction message corresponding to the selection operation is deleted from the dead letter queue.

6. The method according to any one of claims 1 to 5, characterized in that: The data information includes multiple of the transaction serial number, the time when the message enters the dead letter queue, the message number, the message type, the message status, the message source system name, the message source system identity number, the dead letter queue name, the normal queue name and the message details.

7. A transaction message processing device for a dead letter queue, characterized in that: include: The first acquisition module is used to obtain the dead letter queue; A monitoring module, used for monitoring the dead letter queue to identify transaction messages entering the dead letter queue; A second acquisition module, used to acquire data information of the transaction message; A saving module, used for saving the data information of the transaction message to a transaction message data table; A generating module, used for generating an operation interface according to the transaction message data table; The processing module is used to process the transaction message in response to the user's operation on the operation interface.

8. A transaction message processing device for a dead letter queue, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images