Managing queues in an asynchronous messaging system

• US 9,626,235 B2
• Filed: 06/29/2012
• Issued: 04/18/2017
• Est. Priority Date: 10/10/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Blue, George Meldrum, Goddard, Nigel, Gompertz, Martin James, Hickson, Andrew Ian, Longerstaey, Gary Patrick, Willoughby, Philip Graham
• Primary Examiner(s): Kim, Sisley
• Application Number:
  US13/537,641
• Publication Number:
  US 20120272248A1
• Time in Patent Office: 1,754 Days
• Field of Search: None
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method of managing an asynchronous messaging queue with a client computer in an asynchronous messaging system, where the client computer is programmed to store an manage the asynchronous messaging queue, includes receiving a reactive message in the asynchronous messaging queue, the reactive message including an identification of a previously initiated message and an action to be performed on the previously initiated message; and upon determining that the previously initiated message has already been received in the asynchronous messaging queue, performing the action on the previously initiated message with the client computer.

Claims

1. A method of managing an asynchronous messaging queue with a client computer in an asynchronous messaging system, said client computer being programmed to store and manage said asynchronous messaging queue, said method comprising:

receiving a reactive message in said asynchronous messaging queue stored by said client computer, said reactive message comprising a reactive message indicator that the reactive message is reactive, an identification of a previously initiated message and an action to be performed on said previously initiated message;

determining whether the previously initiated message is present in the same asynchronous message queue where the reactive message has been received prior to a final delivery of the previously initiated message to an intended recipient;

responsive to a determination that said previously initiated message is present in that asynchronous messaging queue prior to the final delivery of the previously initiated message to the intended recipient, performing said action specified by the reactive message on said previously initiated message with said client computer prior to final delivery of the previously initiated message to the intended recipient;

responsive to a determination that said previously initiated message has not already been received in said asynchronous messaging queue, storing said reactive message in a reactive message store for subsequent performance of said action on said previously initiated message when said previously initiated message is subsequently available in that asynchronous messaging queue; and

responsive to a determination that at least one reactive message stored in said reactive message store identifies a subsequent message received in said asynchronous messaging queue, performing an action on said subsequent message that is specified by that reactive message which identifies said subsequent message.

2. The method of claim 1, further comprising only storing said reactive message in said reactive message store if a variable attribute of said reactive message indicates that said reactive message is to be stored in said reactive message store.

3. The method of claim 1, further comprising discarding said reactive message after said action is performed on said previously initiated message.

4. The method of claim 1, in which said reactive message identifies a plurality of previously initiated messages and said action applies to each previously initiated method in said plurality, said method further comprising performing said action specified in said reactive message only after each previously initiated message identified by said reactive message has been received in said asynchronous messaging queue.

5. The method of claim 1, in which said action comprises deletion of said previously initiated message.

6. The method of claim 1, in which said action comprises modifying said previously initiated message.

7. The method of claim 1, in which said action comprises redirecting said previously initiated message to another asynchronous messaging queue.

8. The method of claim 1, in which said asynchronous messaging queue comprises a transmission queue associated with a first software entity for storing messages for onward transmission to another asynchronous messaging queue associated with a second software entity separate from said first software entity.

9. The method of claim 1, in which said asynchronous messaging queue comprises a receiving queue associated with a second software entity for receiving messages transmitted from a transmission queue associated with a first software entity.

17. The method of claim 1, further comprising:

responsive to receiving a subsequent message in said asynchronous message queue, determining whether any reactive message stored in said reactive message store identifies that subsequent message.

10. An asynchronous messaging system node, said node comprising:

a processor; and

computer memory communicatively coupled to and readable by said processor, said computer memory being configured to store an asynchronous messaging queue and software, such that said processor, when executing said software, is configured to;

receive a reactive message in said asynchronous messaging queue, said reactive message comprising an identification of a previously initiated message and an action to be performed on said previously initiated message;

search said asynchronous messaging queue to determine whether said previously initiated message has already been received in said asynchronous messaging queue;

responsive to determining that said previously initiated message has already been received in said asynchronous messaging queue, perform said action on said previously initiated message prior to final delivery of the previously initiated message to an intended recipient;

responsive to a determination that said previously initiated message has not already been received in said asynchronous messaging queue, storing said reactive message in a reactive message store for subsequent performance of said action on said previously initiated message; and

responsive to a determination that at least one reactive message stored in said reactive message store identifies a subsequent message received in said asynchronous messaging queue, performing an action on said subsequent message specified by the at least one reactive message identifying said subsequent message.

11. The asynchronous messaging system node of claim 10, in which said processor is further configured to store said reactive message in said reactive message store only if a variable attribute of said reactive message indicates that said reactive message is to be stored in said reactive message store.

12. The asynchronous messaging system node of claim 10, in which said reactive message identifies a plurality of previously initiated messages and said action applies to each previously initiated method in said plurality, said processor being further configured to perform said action specified in said reactive message only after each previously initiated message identified by said reactive message has been received in said asynchronous messaging queue.

13. The asynchronous messaging system node of claim 10, in which said asynchronous messaging queue is a transmit queue such that said action is performed on the previously initiated message prior to transmission of the previously initiated message to a target queue in route to said intended recipient.

14. The asynchronous messaging system node of claim 10, in which said asynchronous messaging queue comprises a reactive agent to which all incoming messages are first directed to determine which messages are reactive messages and which are non-reactive messages.

15. The asynchronous messaging system node of claim 10, in which said asynchronous messaging queue comprises a receiving queue for receiving messages transmitted from a transmission queue associated with a second asynchronous messaging system node.

16. A computer program product for managing an asynchronous messaging queue, the computer program product comprising:

a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising;

computer readable program code configured to receive a reactive message in said asynchronous messaging queue, said reactive message comprising an identification of a previously initiated message and an action to be performed on said previously initiated message;

computer readable program code configured to perform said action on said previously initiated message responsive to a determination that said previously initiated message has already been received in said asynchronous messaging queue prior to a GET call to the asynchronous messaging queue from an application program that is the intended recipient of the previously initiated message;

computer readable program code configured to store said reactive message in a reactive message store responsive to a determination that said previously initiated message has not already been received in said asynchronous messaging queue; and

computer readable program code configured to perform said action on a subsequent message received in said asynchronous message queue in response to a determination that said reactive message stored in said reactive message store identifies said subsequent message.