Optimistic processing of messages in a messaging system

• US 9,442,781 B2
• Filed: 09/14/2006
• Issued: 09/13/2016
• Est. Priority Date: 09/17/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Garza, Jose Emir, Hobson, Stephen James
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): Yun, Carina
• Application Number:
  US11/531,726
• Publication Number:
  US 20070067313A1
• Time in Patent Office: 3,652 Days
• Field of Search: 719/314
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

For processing messages in a messaging system comprising a source and a destination queue manager, an uncommitted message is received from an application at the source queue manager. This is transmitted to the destination queue manager and received thereat. When it is determined that the message is uncommitted, it is stored in memory, rather than placing the message on a receive queue for processing by another application. If it is determined that the uncommitted message has been committed by the application which originated the uncommitted message, then it is placed on the receive queue.

Claims

1. A method for a receiving queue manager to process messages optimistically, the method comprising:

receiving, from a source queue manager, an indication that a message which forms part of a transaction is uncommitted;

determining from the message itself that the message is uncommitted;

storing, in response to the determination that the message is uncommitted, the message in memory, the memory having a table containing details of all uncommitted messages which form other parts of the transaction, the uncommitted messages having an assigned sending identification at the source queue manager that is correlated in the table with a receiving queue manager identification which is assigned when a new transaction is received at the receiving queue manager;

placing, in response to a determination that the transaction has been committed by an application which originated the message, the list of messages, including the uncommitted message, on a receive queue for processing therefrom;

removing, in response to placing the message of the transaction on a receive queue, reference to the transaction and an associated linked list of messages by updating the table; and

deleting, in response to receiving at the destination queue manager an indication that the transaction including the message is to be undone, the transaction from the memory;

wherein the table contains a plurality of entries, each of the plurality of entries contains a specific assigned sending identification and a specific receiving queue manager identification for a specific transaction, and each of the specific sending identification and the specific receiving queue manager identification point to a separate linked list of uncommitted messages owned by the specific transaction, and

wherein each of the linked list of uncommitted messages represents a single transaction.

2. The method of claim 1, wherein storing the message in memory comprises determining whether the other uncommitted messages in the transaction are known.

3. The method of claim 2, wherein storing the message in memory comprises adding, in response to a positive determination, the message to the list.

4. The method of claim 1, comprising:

deleting old messages from the memory in order to free up space for newly received messages at the destination queue manager;

receiving notification that a deleted message has been committed; and

requesting retransmission of the deleted message by the source queue manager.

5. The method of claim 1, comprising:

receiving the uncommitted message at an intermediate queue manager;

forwarding the message as an uncommitted message on its way to the destination queue manager unless a transmission path is unavailable; and

responsive to the transmission path being unavailable, storing the uncommitted message in memory associated with the intermediate queue manager.

6. The method of claim 1, comprising:

responsive to determining that the receiving queue manger is an intermediate queue manager, forwarding the message as an uncommitted message on its way to the destination queue manager unless a transmission path is unavailable; and

responsive to a transmission path being unavailable, storing the uncommitted message in memory associated with the intermediate queue manager.

7. The method of claim 1, comprising, updating the list in memory to remove reference to the committed transaction and the list of messages.

8. An apparatus for a receiving queue manager to process messages optimistically, the apparatus comprising:

a processor;

a memory, operatively coupled to the processor, and having stored thereon instructions executable by the processor to;

receive an uncommitted message from a source queue manager, the uncommitted message forming part of a transaction;

store, in response to a determination that the received message is uncommitted, the message in memory containing a list of uncommitted messages which form other parts of the transaction, the uncommitted messages having an assigned sending identification at the source queue manager that is correlated in a table with a receiving queue manager identification which is assigned when a new transaction is received at the receiving queue manager,

remove, in response to a placement of the message of the transaction on a receive queue, reference to the transaction and an associated linked list of messages by updating the table,

delete, in response to receipt at a destination queue manager, of an indication that the transaction including the received message is to be undone, the transaction from the memory; and

in response to a determination that the transaction has been committed by an application which originated the message, place the list of messages, including the uncommitted message, on a receive queue for processing therefrom;

wherein the table contains a plurality of entries, each of the plurality of entries contains a specific assigned sending identification and a specific receiving queue manager identification for a specific transaction, and each of the specific sending identification and the specific receiving queue manager identification point to a separate linked list of uncommitted messages owned by the specific transaction, and

wherein each of the linked list of uncommitted messages represents a single transaction.

9. The apparatus of claim 8, wherein, responsive to receiving, at the destination queue manager, an indication that the transaction including the received message is to be undone, a storing component is configured to delete the transaction from the memory.

10. The apparatus of claim 9, wherein the storing component is configured to also update the list in memory to remove reference to the committed transaction and the list of messages.

11. A computer program product for a receiving queue manager to process messages optimistically, the computer program product comprising:

a non-transitory computer readable storage medium having computer readable program code tangibly embedded therein, the computer readable program code configured to;

receive, from a source queue manager, an indication that a message which forms part of a transaction is uncommitted;

in response to a determination that the message is uncommitted, store the message in memory, the memory having a table containing details of all uncommitted messages which form other parts of the transaction, the uncommitted messages having an assigned sending identification at the source queue manager that is correlated in the table with a receiving queue manager identification which is assigned when a new transaction is received at receiving queue manager;

in response to a determination that the transaction has been committed by an application which originated the message, place the list of messages, including the uncommitted message, on a receive queue for processing therefrom;

in response to placing the message on a receive queue, remove reference to the transaction and an associated linked list of messages by updating the table; and

in response to receiving, at the destination queue manager, an indication that the transaction including the message is to be undone, delete the transaction from memory;

wherein the table contains a plurality of entries, each of the plurality of entries contains a specific assigned sending identification and a specific receiving queue manager identification for a specific transaction, and each of the specific sending identification and the specific receiving queue manager identification point to a separate linked list of uncommitted messages owned by the specific transaction, and

wherein each of the linked list of uncommitted messages represents a single transaction.

12. The computer program product of claim 11, wherein the computer readable program code is configured to receive an indication that the message is uncommitted from the source queue manager.

13. The computer program product of claim 11, wherein the computer readable program code is configured to determine from the message itself that the message is uncommitted.

14. The computer program product of claim 11, wherein the computer readable program code is configured to:

determine whether other messages in the transaction are known about by the destination queue manager; and

responsive to a positive determination, add the message to a list of the other messages.

15. The computer program product of claim 11, wherein the computer readable program code is configured to update the list in memory to remove reference to the committed transaction and the list of messages.

16. The computer program product of claim 11, wherein the computer readable program code is configured to:

receive, at the destination queue manager, an indication that the transaction including the received message is to be undone; and

delete the transaction from the memory.

17. The computer program product of claim 11, wherein the computer readable program code is configured to:

delete old messages from the memory in order to free up space for newly received messages at the destination queue manager;

receive notification that a deleted message has been committed; and

request retransmission of the deleted message by the source queue manager.

18. The computer program product of claim 11, wherein the computer readable program code is configured to:

receive the uncommitted message at an intermediate queue manager;

forward the message as an uncommitted message on its way to the destination queue manager unless a transmission path is unavailable; and

responsive to the transmission path being unavailable, store the uncommitted message in memory associated with the intermediate queue manager.

19. The computer program product of claim 11, wherein the computer readable program code is configured to:

responsive to determining that the receiving queue manger is an intermediate queue manager, forward the message as an uncommitted message on its way to the destination queue manager unless a transmission path is unavailable; and

responsive to a transmission path being unavailable, store the uncommitted message in memory associated with the intermediate queue manager.