MESSAGE PROCESSING

• US 20120054775A1
• Filed: 08/15/2011
• Published: 03/01/2012
• Est. Priority Date: 08/26/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Garza, Jose E., Hobson, Stephen J.
• Granted Patent: US 9,069,632 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• 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 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;

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

failing the transaction in response to the message sequence number not being greater than the last processed message sequence number.

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:

receiving an originator identifier for the transaction.

4. The method according to claim 3 further comprising:

detecting that there is no message sequence number stored for the identified originator, and, in response, storing the message sequence number for the identified originator.

5. 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.

6. 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.

7. A computer program product embodied in a computer readable storage medium for operating a transaction manager, the computer program product comprising the programming instructions for:

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;

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

failing the transaction in response to the message sequence number not being greater than the last processed message sequence number.

8. The computer program product according to claim 7 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.

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

receiving an originator identifier for the transaction.

10. The computer program product according to claim 9 further comprising the programming instructions for:

detecting that there is no message sequence number stored for the identified originator, and, in response, storing the message sequence number for the identified originator.

11. The computer program product according to claim 7 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.

12. The computer program product according to claim 7 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.

13. A system, comprising:

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

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

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;

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

circuitry for failing the transaction in response to the message sequence number not being greater than the last processed message sequence number.

14. The system according to claim 13, wherein said 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.

15. The system according to claim 13, wherein said processor further comprises:

circuitry for receiving an originator identifier for the transaction.

16. The system according to claim 15, wherein said processor further comprises:

circuitry for detecting that there is no message sequence number stored for the identified originator, and, in response, storing the message sequence number for the identified originator.

17. The system according to claim 13, wherein said 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.

18. The system according to claim 13, wherein said 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.