Message processing

• US 9,069,632 B2
• Filed: 08/15/2011
• Issued: 06/30/2015
• Est. Priority Date: 08/26/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Garza, Jose E., Hobson, Stephen J.
• Primary Examiner(s): Mudrick, Timothy A
• Application Number:
  US13/209,623
• Publication Number:
  US 20120054775A1
• Time in Patent Office: 1,415 Days
• Field of Search: 719/314
• US Class Current: 1/1
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method, system and computer program product for operating a transaction manager. An invocation to begin a transaction as well as a message sequence number for the transaction are received. It is then determined if the message sequence number is greater than the last processed message sequence number. If the message sequence number is greater than the last processed message sequence number, then the transaction is started. Otherwise, if the message sequence number is not greater than the last processed message sequence number, then the transaction is failed.

Claims

1. A method of operating a transaction manager, the method comprising:

receiving multiple copies of a message using independent paths through a messaging network, wherein each of said independent paths comprises a queue;

receiving an invocation to begin a transaction;

receiving a message sequence number for the transaction;

checking, by a processor, that the message sequence number is greater than a last processed message sequence number for each message received;

starting the transaction in response to the message sequence number being greater than the last processed message sequence number;

failing the transaction in response to the message sequence number being less than the last processed message sequence number;

invoking a receiver agent by a consuming application to delete a message associated with the message sequence number in response to failing the transaction;

receiving an original identifier for the transaction; and

detecting that there is no message sequence number stored for the message associated with the original identifier, and, in response, storing the message sequence number for the message associated with the original identifier.

2. The method according to claim 1 further comprising:

recording the message sequence number and a decision to complete or backout the transaction as a single write to a log.

3. The method according to claim 1 further comprising:

detecting that the message sequence number is greater than one more than the last processed message sequence number and reporting a missing message sequence number.

4. The method according to claim 1 further comprising:

detecting that the message sequence number is equal to a message sequence number for an invoked transaction that is not yet complete and reporting a busy code.

5. A computer program product embodied in a computer readable storage medium, wherein the medium does not include a propagating signal, for operating a transaction manager, the computer program product comprising the programming instructions for:

receiving multiple copies of a message using independent paths through a messaging network, wherein each of said independent paths comprises a queue;

receiving an invocation to begin a transaction;

receiving a message sequence number for the transaction;

checking that the message sequence number is greater than a last processed message sequence number for each message received;

starting the transaction in response to the message sequence number being greater than the last processed message sequence number;

failing the transaction in response to the message sequence number being less than the last processed message sequence number;

invoking a receiver agent by a consuming application to delete a message associated with the message sequence number in response to failing the transaction;

receiving an original identifier for the transaction; and

detecting that there is no message sequence number stored for the message associated with the original identifier, and, in response, storing the message sequence number for the message associated with the original identifier.

6. The computer program product according to claim 5 further comprising the programming instructions for:

recording the message sequence number and a decision to complete or backout the transaction as a single write to a log.

7. The computer program product according to claim 5 further comprising the programming instructions for:

detecting that the message sequence number is greater than one more than the last processed message sequence number and reporting a missing message sequence number.

8. The computer program product according to claim 5 further comprising the programming instructions for:

detecting that the message sequence number is equal to a message sequence number for an invoked transaction that is not yet complete and reporting a busy code.

9. A system, comprising:

a memory unit for storing a computer program for operating a transaction manager; and

a processor coupled to the memory unit, wherein the processor, responsive to the computer program, comprises;

circuitry for receiving multiple copies of a message using independent paths through a messaging network, wherein each of said independent paths comprises a queue;

circuitry for receiving an invocation to begin a transaction;

circuitry for receiving a message sequence number for the transaction;

circuitry for checking that the message sequence number is greater than a last processed message sequence number for each message received;

circuitry for starting the transaction in response to the message sequence number being greater than the last processed message sequence number;

circuitry for failing the transaction in response to the message sequence number being less than the last processed message sequence number;

circuitry for invoking a receiver agent by a consuming application to delete a message associated with the message sequence number in response to failing the transaction;

circuitry for receiving an original identifier for the transaction; and

circuitry for detecting that there is no message sequence number stored for the message associated with the original identifier, and, in response, storing the message sequence number for the message associated with the original identifier.

10. The system according to claim 9, wherein the processor further comprises:

circuitry for recording the message sequence number and a decision to complete or backout the transaction as a single write to a log.

11. The system according to claim 9, wherein the processor further comprises:

circuitry for detecting that the message sequence number is greater than one more than the last processed message sequence number and reporting a missing message sequence number.

12. The system according to claim 9, wherein the processor further comprises:

circuitry for detecting that the message sequence number is equal to a message sequence number for an invoked transaction that is not yet complete and reporting a busy code.