SELECTIVE MESSAGE REPUBLISHING TO SUBSCRIBER SUBSETS IN A PUBLISH-SUBSCRIBE MODEL

• US 20160087923A1
• Filed: 04/17/2015
• Published: 03/24/2016
• Est. Priority Date: 09/23/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: THYAGARAJ, LOHITASHWA, KESAVAN, SANJAY M., LALGOWDAR, RAJESH, SAMANTARAY, SONALI
• Granted Patent: US 9,654,433 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

According to one exemplary embodiment, a method for selectively resending a first message in a publish-subscribe message distribution model is provided. The method may include receiving the first message having a first message ID associated with the first message. The method may include sending the first message to a plurality of subscribers. The method may include receiving a rolled back first message. The method may include determining if the first message ID matches a second message ID associated with a second message. The method may include creating a first subscriber list associated with the first message. The method may include storing the first message in a data structure. The method may include appending a second subscriber list associated with the second message with a subscriber. The method may include sending the second message to the first subscriber or the first message to the first subscriber.

Claims

1. A method for selectively resending a first message in a publish-subscribe message distribution model, the method comprising:

receiving the first message, wherein the first message has a first message identification (ID) associated with the first message;

sending the received first message to a plurality of subscribers;

receiving a rolled back first message from a first subscriber;

determining if the first message ID associated with the first message matches a second message ID associated with a second message, wherein the second message is stored in a data structure;

creating a first subscriber list associated with the rolled back first message, wherein the first subscriber list includes a subscriber identifier corresponding with the first subscriber based on the determining that the first message ID does not match the second message ID;

storing the first message in the data structure based on the determining that the first message ID does not match the second message ID;

appending a second subscriber list associated with the second message to include the subscriber identifier associated with the first subscriber based on the determining that the first message ID matches the second message ID; and

sending the second message to the first subscriber based on the appending the second subscriber list or the first message to the first subscriber based on the storing the first message in the data structure.

2. The method of claim 1, further comprising:

resending the rolled back first message to the first subscriber a predetermined number of times.

3. The method of claim 1, wherein the receiving the rolled back first message from the first subscriber comprises the first subscriber encountering an issue attempting to process the first message and rolling back the first message.

4. The method of claim 1, wherein the data structure comprises an exception queue.

5. The method of claim 1, wherein the first subscriber is a non-durable subscriber.

6. The method of claim 5, wherein the subscriber identifier associated with the first subscriber is valid until the first subscriber disconnects from a messaging oriented middleware system.

7. The method of claim 1, further comprising:

determining if the rolled back first message should be resent to the first subscriber.