CN112865927B - Message delivery verification method, device, computer equipment and storage medium - Google Patents

Message delivery verification method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN112865927B
CN112865927B CN201911179795.6A CN201911179795A CN112865927B CN 112865927 B CN112865927 B CN 112865927B CN 201911179795 A CN201911179795 A CN 201911179795A CN 112865927 B CN112865927 B CN 112865927B
Authority
CN
China
Prior art keywords
message
sent
middleware
preset time
attribute
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
Application number
CN201911179795.6A
Other languages
Chinese (zh)
Other versions
CN112865927A (en
Inventor
陈曦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Dasou Vehicle Software Technology Co Ltd
Original Assignee
Zhejiang Dasou Vehicle Software Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhejiang Dasou Vehicle Software Technology Co Ltd filed Critical Zhejiang Dasou Vehicle Software Technology Co Ltd
Priority to CN201911179795.6A priority Critical patent/CN112865927B/en
Publication of CN112865927A publication Critical patent/CN112865927A/en
Application granted granted Critical
Publication of CN112865927B publication Critical patent/CN112865927B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682Policies or rules for updating, deleting or replacing the stored data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/548Queue

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application relates to a message delivery verification method, a message delivery verification device, a computer device and a storage medium. The method comprises the following steps: inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender; and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed. The message delivery verification method, the message delivery verification device, the computer equipment and the storage medium continuously detect whether the message is received by the receiver within the preset time, so that the sender knows whether the message is received by the receiver in time and reacts in time, and the message delivery verification method, the message delivery verification device, the computer equipment and the storage medium are high in reliability and high in efficiency.

Description

Message delivery verification method, device, computer equipment and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and apparatus for verifying delivery of a message, a computer device, and a storage medium.
Background
The message is the carrier of the information. In order for both the message sender and the message receiver to understand the information carried by the message, they need to describe the message in a uniform format, known as the message protocol.
There are also two ways in which a message may be sent from a sender to a recipient. One may call instant messaging, i.e., a message sent from one end (message sender) to the other end (message receiver), a specific implementation of this approach is called RPC (Remote Procedure Call, remote method invocation); another way is called delayed messaging, i.e. after a message is sent from one end, it is first stored temporarily in a container and after a certain condition is reached, it is sent from this container to the other end. One specific implementation of this container is a message queue.
The traditional delayed message communication mode is originally for decoupling, but in the actual use process, a sender cannot know whether a receiver receives a message or not after sending the message, cannot respond in time, and has insufficient reliability and lower efficiency.
Disclosure of Invention
Based on this, it is necessary to provide a message delivery verification method, device, computer equipment and storage medium for the technical problems that in the actual use process, the sender cannot know whether the receiver receives after sending the message, cannot respond in time, and has insufficient reliability and low efficiency.
A method of message delivery verification, the method comprising:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
In one embodiment, the verifying the delivery of the sent message based on the preset time further includes:
if the removal signal returned by the receiver is not received within the preset time, the sent message is not sent, and an alarm signal is sent.
In one of the embodiments of the present application,
the querying the message attribute of the sent message from the middleware comprises the following steps:
the message theme, the message object, the message number and the preset time are queried from the middleware.
In one embodiment, the message attributes comprise a plurality of message objects.
In one embodiment, the removal signal includes a message topic, a message object, and a message number.
In one embodiment, said removing said message attributes in said middleware comprises:
and acquiring and removing the corresponding message attribute based on the message theme, the message object and the message number.
In one embodiment, if the removal signal returned by the receiving party is not received within the preset time, the sent message is not sent, and sending the alarm signal further includes:
detecting all overtime messages in the middleware, wherein the message attributes of all overtime messages are not removed in preset time;
sending an alarm signal to an early warning group of an application program corresponding to the overtime message; if the overtime message has no corresponding application program, sending an alarm signal to a preset alarm group;
and deleting message attributes corresponding to the overtime messages in the middleware in batches.
A message delivery verification apparatus, the apparatus comprising:
the inquiry module is used for inquiring the message attribute of the sent message from the middleware, wherein the message attribute of the sent message stored in the middleware is written by the sender;
the acquisition module is used for acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and the judging module is used for verifying the delivery condition of the sent message based on the preset time, and if the removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
A computer device comprising a memory storing a computer program and a processor which when executing the computer program performs the steps of:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
The message delivery verification method, the message delivery verification device, the computer equipment and the storage medium are characterized in that the message attribute of the sent message is inquired from the middleware, wherein the message attribute of the sent message stored in the middleware is written by a sender; acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message; and verifying the sending condition of the sent message based on the preset time, if a removal signal returned by the receiver is received within the preset time, the sent message is sent, and the method for removing the message attribute in the middleware continuously detects whether the receiver receives the message within the preset time, so that the sender knows whether the receiver receives the message in time and reacts in time, and the method is high in reliability and efficiency.
Drawings
FIG. 1 is a diagram illustrating a message delivery verification method according to an embodiment of the present application;
FIG. 2 is a diagram illustrating a message delivery verification method according to an embodiment of the present application;
FIG. 3 is a block diagram illustrating a message delivery verification device according to an embodiment of the present application;
fig. 4 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
Referring to fig. 1, fig. 1 is a schematic diagram of a message delivery verification method according to an embodiment of the application.
In this embodiment, the message delivery verification method includes:
step 100, inquiring the message attribute of the sent message from the middleware, wherein the message attribute of the sent message stored in the middleware is written by the sender.
Illustratively, the message attributes are information about the transmitted message.
It can be appreciated that the middleware is a temporary storage system of message attributes corresponding to the sent message, and specifically, may be a redis storage system.
Redis (full name: remote Dictionary Server remote dictionary service) is an open source log-type, key-Value database written in ANSI C language, supporting network, capable of being based on memory and persistent, and provides multiple language APIs. redis is similar to Memcached in that it supports relatively many more value types stored, including string, list, set, zset (ordered set), and hash (hash type). These data types all support push/pop, add/remove, and pick intersection union and difference and richer operations, and these operations are all atomic. On this basis, redis supports a variety of different ways of ordering. Like memcached, data is cached in memory to ensure efficiency. Except that redis will periodically write updated data to disk or modify operations to additional record files, and master-slave synchronization is implemented on this basis.
Redis is a high-performance key-value database. The occurrence of redis largely compensates the deficiency of key/value storage such as memcached, and can play a good role in supplementing a relational database in partial occasions. The system provides clients such as Java, C/C++, C#, PHP, javaScript, perl, object-C, python, ruby, erlang and the like, and is convenient to use.
Redis supports master-slave synchronization. The data may be synchronized from the master server to any number of slave servers, which may be master servers associated with other slave servers. This allows Redis to perform single-level tree replication. The inventory may write data intentionally and unintentionally. The publish/subscribe mechanism is fully implemented, so that when the slave database synchronizes the tree anywhere, a channel can be subscribed to and the complete message publication record of the master server can be received. Synchronization is helpful for scalability and data redundancy of read operations.
Step 110, acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message.
It can be understood that the preset time of each sent message is different and is correspondingly stored in the message attribute of the sent message, and the preset time corresponding to each sent message is obtained according to the message attribute.
And step 120, verifying the delivery condition of the sent message based on the preset time, and if the removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
It can be understood that if the receiving party receives the message, the verification result is sent, a removal signal is returned, and the message attribute in the middleware is removed after the removal signal is received.
According to the message delivery verification method, whether the message is received by the receiver within the preset time is continuously detected, so that the sender timely knows whether the message is received by the receiver and timely reacts, the reliability is high, and the efficiency is high.
Illustratively, the message attributes of the sent message include querying the middleware for the message topic, the message object, the message number, and the preset time. It can be understood that the message topic is the topic of the sent message, the message object is the receiver of the sent message, the message number is the number of the sent message at the sender, and the preset time is the preset time corresponding to the sent message. It can be appreciated that the correspondence between the message topic, the message object and the preset time is obtained through the Zookeeper.
The ZooKeeper is a distributed application coordination service of open source codes, is an open source implementation of Chubbby of Google, and is an important component of Hadoop and Hbase. It is a software providing a consistency service for distributed applications, the provided functions include: configuration maintenance, domain name service, distributed synchronization, group service, etc. The goal of the ZooKeeper is to package complex and error-prone key services and provide a simple and easy-to-use interface and a system with high performance and stable functions for users.
Specifically, the sent message may be sent to multiple receivers at the same time, that is, the message attribute may include multiple message objects, and when a receiver returns a removal signal within a preset time, the message attribute corresponding to the receiver is removed.
It will be appreciated that when there are multiple recipients of the same message, then multiple message attributes are obtained from the middleware, the number of message attributes being the same as the number of recipients. Specifically, message attributes of multiple recipients of the same message are written by the sender in batch operation using the pipeline mode of the Redis system.
In other embodiments, verifying the delivery of the sent message based on the preset time further includes sending an alarm signal if the removal signal returned by the receiver is not received within the preset time.
In other embodiments, sending the alert signal includes sending the alert signal to an application corresponding to the message object. It will be appreciated that each application of the sender is responsible for sending messages to different receivers, and when a receiver does not return a removal signal within a preset time, an alarm signal is sent to the application corresponding to the receiver. And if the receiver does not have the corresponding application program, sending an alarm signal to a default alarm application program.
In other embodiments, the removal signal includes a message topic, a message object, a message number, and a preset time. It will be appreciated that upon receipt of the removal signal, a corresponding message attribute is found based on the received message topic, message object and message number and removed.
In other embodiments, the method further includes removing message attributes corresponding to the alarm signal after sending the alarm signal.
In other embodiments, if the removal signal returned by the receiver is not received within the preset time, the sent message is not sent, and sending the alarm signal further includes detecting all timeout messages in the middleware without removing the message attribute within the preset time; sending an alarm signal to an early warning group of an application program corresponding to the overtime message; if the overtime message has no corresponding application program, sending an alarm signal to a preset alarm group; and deleting message attributes corresponding to the overtime messages in the middleware in batches. Specifically, detecting all timeout messages in the middleware for which the message attributes have not been removed within the preset time includes detecting all timeout messages using a "ZRANGEBYSCORE" command (ZRANGEBYSCORE zset currentTime +inf).
Referring to fig. 2, fig. 2 is a schematic diagram corresponding to a message delivery verification method according to an embodiment of the application.
It will be appreciated that the message sender sends a message to the message queue and simultaneously sends a message attribute to the redis storage system, and the receiver obtains a message from the message queue and simultaneously sends a removal signal to the redis storage system, which removes the message attribute. The monitoring unit monitors the condition of the redis storage system, and if the message attribute in the redis storage system is not removed within the preset time, an alarm signal is sent. It is understood that the redis storage system is the middleware.
It should be understood that, although the steps in the flowchart of fig. 1 are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 1 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor do the order in which the sub-steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of other steps or sub-steps of other steps.
In one embodiment, as shown in fig. 3, there is provided a message delivery verification apparatus including: a query module 200, an acquisition module 210, and a determination module 220, wherein:
and a query module 200, configured to query the middleware for the message attribute of the sent message, where the message attribute of the sent message stored in the middleware is written by the sender.
The query module 200 is configured to query the middleware for a message topic, a message object, a message number, and a preset time.
The obtaining module 210 is configured to obtain a preset time based on a message attribute, where the message attribute includes a preset time corresponding to the sent message.
And the judging module 220 is configured to verify the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, so as to remove the message attribute in the middleware.
The judging module 220 is further configured to send an alarm signal if the removal signal returned by the receiving party is not received within a preset time, and the sent message is not sent.
The judging module 220 is further configured to obtain and remove the corresponding message attribute based on the message theme, the message object and the message number.
For specific limitations on the message delivery verification device, reference may be made to the above limitations on the message delivery verification method, and no further description is given here. The various modules in the message delivery verification device described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 4. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a message delivery verification method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by persons skilled in the art that the architecture shown in fig. 4 is merely a block diagram of some of the architecture relevant to the present inventive arrangements and is not limiting as to the computer device to which the present inventive arrangements are applicable, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
In one embodiment, the processor when executing the computer program further performs the steps of:
if the removal signal returned by the receiver is not received within the preset time, the sent message is not sent, and an alarm signal is sent.
In one embodiment, the processor when executing the computer program further performs the steps of:
the message theme, the message object, the message number and the preset time are queried from the middleware.
In one embodiment, the processor when executing the computer program further performs the steps of:
and acquiring and removing the corresponding message attribute based on the message theme, the message object and the message number.
In one embodiment, the processor when executing the computer program further performs the steps of:
detecting all overtime messages in the middleware, wherein the message attributes of all overtime messages are not removed in preset time;
sending an alarm signal to an early warning group of an application program corresponding to the overtime message; if the overtime message has no corresponding application program, sending an alarm signal to a preset alarm group;
and deleting message attributes corresponding to the overtime messages in the middleware in batches.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
In one embodiment, the computer program when executed by the processor further performs the steps of:
if the removal signal returned by the receiver is not received within the preset time, the sent message is not sent, and an alarm signal is sent.
In one embodiment, the computer program when executed by the processor further performs the steps of:
the message theme, the message object, the message number and the preset time are queried from the middleware.
In one embodiment, the computer program when executed by the processor further performs the steps of:
and acquiring and removing the corresponding message attribute based on the message theme, the message object and the message number.
In one embodiment, the computer program when executed by the processor further performs the steps of:
detecting all overtime messages in the middleware, wherein the message attributes of all overtime messages are not removed in preset time;
sending an alarm signal to an early warning group of an application program corresponding to the overtime message; if the overtime message has no corresponding application program, sending an alarm signal to a preset alarm group;
and deleting message attributes corresponding to the overtime messages in the middleware in batches.
The message delivery verification method, the message delivery verification device, the computer equipment and the storage medium are characterized in that the message attribute of the sent message is inquired from the middleware, wherein the message attribute of the sent message stored in the middleware is written by a sender; acquiring preset time based on the message attribute; and verifying the sending condition of the sent message based on the preset time, if the removal signal is received in the preset time, the sent message is sent, and the method for removing the message attribute in the middleware continuously detects whether the message is received by the receiver in the preset time, so that the sender knows whether the message is received by the receiver in time and reacts in time, and the reliability is high and the efficiency is high.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.

Claims (10)

1. A method of message delivery verification, wherein a sender sends a message to a message queue and simultaneously sends message attributes to middleware, the method comprising:
inquiring message attributes of sent messages from middleware, wherein the message attributes of the sent messages stored in the middleware are written by a sender; the middleware is a temporary storage system of message attributes corresponding to the sent message;
acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and verifying the delivery condition of the sent message based on the preset time, and if a removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
2. The message delivery verification method according to claim 1, wherein the verifying delivery of the transmitted message based on the preset time further comprises:
if the removal signal returned by the receiver is not received within the preset time, the sent message is not sent, and an alarm signal is sent.
3. The messaging verification method of claim 1, wherein querying the message attributes of the sent message from the middleware comprises:
the message theme, the message object, the message number and the preset time are queried from the middleware.
4. A messaging verification method according to claim 3, wherein said message attributes comprise a plurality of said message objects.
5. The messaging verification method of claim 1, wherein the removal signal comprises a message topic, a message object, and a message number.
6. The messaging verification method of claim 5, wherein said removing said message attributes in said middleware comprises:
and acquiring and removing the corresponding message attribute based on the message theme, the message object and the message number.
7. The message delivery verification method according to claim 1, wherein if the removal signal returned by the receiver is not received within a preset time, the sent message is not delivered, and sending the alarm signal further comprises:
detecting all overtime messages in the middleware, wherein the message attributes of all overtime messages are not removed in preset time;
sending an alarm signal to an early warning group of an application program corresponding to the overtime message; if the overtime message has no corresponding application program, sending an alarm signal to a preset alarm group;
and deleting message attributes corresponding to the overtime messages in the middleware in batches.
8. A message delivery verification apparatus, wherein a sender sends a message into a message queue and simultaneously sends message attributes into middleware, the apparatus comprising:
the inquiry module is used for inquiring the message attribute of the sent message from the middleware, wherein the message attribute of the sent message stored in the middleware is written by the sender; the middleware is a temporary storage system of message attributes corresponding to the sent message;
the acquisition module is used for acquiring preset time based on the message attribute, wherein the message attribute comprises the preset time corresponding to the sent message;
and the judging module is used for verifying the delivery condition of the sent message based on the preset time, and if the removal signal returned by the receiver is received in the preset time, the sent message is delivered, and the message attribute in the middleware is removed.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 8 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 8.
CN201911179795.6A 2019-11-27 2019-11-27 Message delivery verification method, device, computer equipment and storage medium Active CN112865927B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911179795.6A CN112865927B (en) 2019-11-27 2019-11-27 Message delivery verification method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911179795.6A CN112865927B (en) 2019-11-27 2019-11-27 Message delivery verification method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112865927A CN112865927A (en) 2021-05-28
CN112865927B true CN112865927B (en) 2023-09-12

Family

ID=75985397

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911179795.6A Active CN112865927B (en) 2019-11-27 2019-11-27 Message delivery verification method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112865927B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205325B (en) * 2021-12-17 2023-08-04 平安壹钱包电子商务有限公司 Message sending method, device, server and storage medium
CN115269235B (en) * 2022-09-28 2022-12-23 深圳华锐分布式技术股份有限公司 Message carrying method, device, equipment and medium based on components of different versions

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7162512B1 (en) * 2000-02-28 2007-01-09 Microsoft Corporation Guaranteed exactly once delivery of messages
CN101931912A (en) * 2010-08-25 2010-12-29 中兴通讯股份有限公司 Method for transmitting notification message and multimedia message service center
CN102368700A (en) * 2011-10-25 2012-03-07 曙光信息产业(北京)有限公司 Transmission method of massages in distributed system
CN105634692A (en) * 2015-12-24 2016-06-01 天津交控科技有限公司 Data packet transmitting method and receiving method based on UDP protocol
CN107483316A (en) * 2016-09-29 2017-12-15 维沃移动通信有限公司 A kind of information transferring method and mobile terminal
CN107682324A (en) * 2017-09-20 2018-02-09 华胜信泰信息产业发展有限公司 Method for message transmission, system, storage medium and computer equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7162512B1 (en) * 2000-02-28 2007-01-09 Microsoft Corporation Guaranteed exactly once delivery of messages
CN101931912A (en) * 2010-08-25 2010-12-29 中兴通讯股份有限公司 Method for transmitting notification message and multimedia message service center
CN102368700A (en) * 2011-10-25 2012-03-07 曙光信息产业(北京)有限公司 Transmission method of massages in distributed system
CN105634692A (en) * 2015-12-24 2016-06-01 天津交控科技有限公司 Data packet transmitting method and receiving method based on UDP protocol
CN107483316A (en) * 2016-09-29 2017-12-15 维沃移动通信有限公司 A kind of information transferring method and mobile terminal
CN107682324A (en) * 2017-09-20 2018-02-09 华胜信泰信息产业发展有限公司 Method for message transmission, system, storage medium and computer equipment

Also Published As

Publication number Publication date
CN112865927A (en) 2021-05-28

Similar Documents

Publication Publication Date Title
WO2021180025A1 (en) Message processing method and apparatus, electronic device and medium
CN111585867B (en) Message processing method and device, electronic equipment and readable storage medium
US10579595B2 (en) Method and device for calling a distributed file system
US11385830B2 (en) Data storage method, apparatus and system, and server, control node and medium
CN111159233B (en) Distributed caching method, system, computer equipment and storage medium
CN111641700B (en) Ceph object-based management and retrieval implementation method for storage metadata
CN110008041B (en) Message processing method and device
CN112865927B (en) Message delivery verification method, device, computer equipment and storage medium
CN111338834B (en) Data storage method and device
CN111010318A (en) Method and system for discovering loss of connection of terminal equipment of Internet of things and equipment shadow server
CN113127232A (en) Message processing method, device, equipment and storage medium
US20150039759A1 (en) Apparatus, method, and non-transitory computer readable storage medium thereof for controlling access of a resource
CN111327680B (en) Authentication data synchronization method, device, system, computer equipment and storage medium
CN112860746B (en) Cache reduction-based method, equipment and system
CN113535477B (en) Method and equipment for data disaster recovery
CN111294231B (en) Resource management method and system
CN103701667A (en) Method, device and system for monitoring heartbeat of server
CN111400327B (en) Data synchronization method and device, electronic equipment and storage medium
CN107704557B (en) Processing method and device for operating mutually exclusive data, computer equipment and storage medium
CN112818166A (en) Video information query method and device, electronic equipment and storage medium
CN112905550A (en) Data export method and device
CN111291127A (en) Data synchronization method, device, server and storage medium
CN115529288B (en) Message pushing method, device and computer equipment
CN111444200A (en) Data updating method and storage medium
CN103699666A (en) Transmission method and transmission device for splitting data

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant