Duplicate message elimination system for a message broker

• US 20040205770A1
• Filed: 02/11/2003
• Published: 10/14/2004
• Est. Priority Date: 02/11/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Astl, Kenneth L., Sundaramurthy, Arul Prabhu, Gooty, Subramanyam Agraharam, Zhang, Kai Mike
• Application Number:
  US10/364,738
• Publication Number:
  US 20040205770A1
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method for preventing the delivery of duplicate messages in a message system, wherein each message comprises a unique message identifier that identifies itself from adjacent messages, comprises the steps of polling a message store for messages directed to a specified receiver; receiving from the message store at least one message directed to the specified receiver; processing the at least one message; receiving, from a monitor queue, a message identifier for the last message successfully delivered to the specified receiver; and comparing the message identifier received from the monitor queue to the message identifier of the message received from the message store.

Claims

1. A method for preventing delivery of duplicate messages in a message system, wherein each message comprises a unique message identifier;

the method comprising the steps of;

polling a message store for messages;

retrieving from the message store at least one message;

processing the at least one message;

retrieving a message identifier from a monitor queue in a transactional server, the message identifier corresponding to the last successfully delivered message; and

comparing the message identifier retrieved from the monitor queue to the message identifier of the message retrieved from the message store.

2. The method of claim 1 wherein if the compared message identifiers do not match the method further comprises the steps of:

sending the at least one message retrieved from the message store to a destination queue in a message broker; and

sending to the monitor queue the unique identifier of the last message successfully delivered.

3. The method of claim 1 wherein if the compared message identifiers match, the method further comprises the step of:

removing the at least one message from the message store upon acknowledgement that the message was successfully delivered.

4. The method of claim 1 wherein if the compared message identifiers match, the method further comprises the step of:

tagging the at least one message from the message store for non-delivery upon acknowledgement that the message was successfully delivered.

5. The method of claim 1 wherein the monitor queue operates in a transactional message broker server, operating according to the Java Messaging Service application program interface.

6. The method of claim 5 wherein the message store operates in the same message broker server as the monitor queue, according to the Java Messaging Service application program interface.

7. A message system wherein each message comprises a unique identifier that identifies itself from adjacent messages, the message system comprising:

a message transfer agent for processing messages, comprising logic for;

retrieving a message from a message store; and

comparing the unique identifier for the retrieved message to the unique identifier for the message which was last successfully delivered; and

if the compared identifiers do not match, sending the retrieved message to a transactional server for storage in a destination queue; and

sending the unique identifier for the retrieved message to a monitor queue for storage in a monitor queue in a transactional server.

8. The message system of claim 7 further comprising:

a message broker for receiving messages sent by the message store, comprising;

the destination queue for storing messages to be delivered to designated recipients; and

the monitor queue for storing the unique identifier for the last successfully delivered message.

9. The message system of claim 7, wherein the message transfer agent further comprises logic for acknowledging to the message store the transmission of the retrieved message, so that the message store does not serve the message another time, if the compared identifiers match.

10. The message system of claim 7, further comprising a message store for storing source messages.

11. The message system of claim 7 comprising a Java Messaging Service server comprising the monitor queue and the destination queue.

12. A transactional server comprising:

a message broker for receiving messages sent from a message store and for serving the messages on recipients, wherein the message broker comprises a delivery queue and a monitor queue for storing an identifier corresponding to the last message successfully delivered.

13. The transactional server of claim 12, further comprising:

an agent for performing the following logic;

polling the message store for messages, receiving at least one message responsive to the polling;

processing the at least one message;

and sending the at least one message to the message broker;

wherein the message server comprises a destination queue and a monitor queue for storing the message identifier for the last successfully delivered message; and

wherein the agent is configured to retrieve the identifier stored in the monitor queue and to compare the retrieved identifier with the identifier from the message retrieved from the message store, and acknowledging the message store so that the message store removes the message from storage if the retrieved identifier matches the current message retrieved from the message store.

14. The transactional server of claim 13, wherein the agent further comprises logic to send the current message identifier to the monitor queue and to send the current message to the destination queue if the retrieved identifier does not match the current message identifier from the message retrieved from the message store.

15. The transactional server of claim 12, comprising a Java Messaging Service server that comprises the message broker.

16. The transactional server of claim 12 further comprising the message store, which comprises a persistent storage system for storing source messages.

17. The transactional server of claim 12 wherein the message store comprises a Java Messaging Service queue for storing source messages.

18. The transactional server of claim 12 wherein the message store comprises a database table for storing the source messages.

19. A program product comprising instructions for causing a processor to:

poll a message store for messages directed to a specified receiver;

receive from the message store at least one message directed to the specified receiver;

process the at least one message;

receive, from a monitor queue, a message identifier for the last message successfully delivered to the specified receiver; and

compare the message identifier received from the monitor queue to the message identifier of the message received from the message store.

20. The program product of claim 19 further comprising the instruction of sending the at least one message received from the message store to a destination queue in a message broker if the compared message identifiers do not match.

21. The program product of claim 19 further comprising the instruction of sending the message identifier from the message retrieved from the message store to the monitor queue in a message broker if the compared message identifiers do not match.