Systems and methods for multi-stage message brokering

• US 7,653,679 B2
• Filed: 08/15/2002
• Issued: 01/26/2010
• Est. Priority Date: 08/16/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Patterson, Andrew, Sadler, Andrew, Turvey, David, Kantor, Jiri, McMillan, Craig, Bevis, Paul
• Primary Examiner(s): Srivastava; Vivek
• Assistant Examiner(s): Pollack; Melvin H
• Application Number:
  US10/219,461
• Publication Number:
  US 20030126229A1
• Time in Patent Office: 2,721 Days
• Field of Search: 709/201, 709/203, 709/219, 709/221, 709/223, 709/224, 709/248, 709/227, 714 15- 21, 714/4, 718/101, 719/314, 705/35
• US Class Current: 709/201
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G07F 7/1016 Devices or methods for securing the PIN and other transaction-data, e.g. by encryption arrangements for secret communication, see H04L9/00

Abstract

A message brokering mechanism for performing a recovery operation in a transaction processing system including first and second stages operable to exchange message requests and responses. The first stage may receive a message request from a message source and may check whether the message request is a special message request. This may be by way of checking if a recovery attribute of the message request is set. A normal message request may have a recovery attribute that is not set. If the message request is a special message request, it may be dispatched to the second stage. If the message request is a normal message request, it may be dispatched to the second stage if the normal message request is not a repeat normal message request.

Claims

1. An apparatus comprising:

one or more processors; and

a storage device storing program instructions executable by the one or more processors to implement a message brokering mechanism including;

a first stage operable to interface with a message source, wherein the first stage is configured to maintain a first set of records identifying message requests received from the message source and message responses sent to the message source;

a second stage operable to interface with a message processor, wherein the second stage is configured to maintain a second set of records identifying message requests sent to the message processor and message responses received from the message processor; and

a recovery mechanism;

wherein the first stage is configured to determine whether a normal message request received from the message source is a duplicate request and, if the normal message request is not a duplicate request, to dispatch the normal message request to the second stage, and, if the normal message request is a duplicate request, to send a message response to the message source without dispatching the normal message request to the second stage;

wherein, in response to receiving the normal message request, the second stage is configured to send the normal message request to the message processor and, if a message response is received from the message processor, to dispatch the message response to the first stage for sending to the message source;

wherein, in response to receiving a recovery process activation message, the recovery mechanism is configured to access each of the first and second sets of records to identify those message requests for which a corresponding message response is not included indicating that the message request has been processed and to convert each such message request into a corresponding special message request; and

wherein, in response to receiving a given special message request, the second stage is configured to send a corresponding request to the message processor and to start a timer process and, if a response is not received from the message processor within a designated time period as dictated by the timer process, to identify the corresponding request as a failed request.

2. The apparatus as recited in claim 1 wherein, in response to determining that the normal message request is a duplicate request, the first stage is further configured to determine whether an existing message response is included in the first set of records.

3. The apparatus as recited in claim 2 wherein, in response to determining that an existing message response is included in the first set of records, the first stage is further configured to send the existing message response to the message source.

4. The apparatus as recited in claim 2 wherein, in response to determining that an existing message response is not included in the first set of records, the first stage is further configured to send an in progress message response to the message source.

5. The apparatus as recited in claim 1 wherein, in response to receiving the given special message request, the second stage is configured to determine whether an existing response message to the given special message request is included in the second set of records and, if so, to send the existing response to the first stage for forwarding to the message source instead of sending the corresponding request to the message processor and starting the timer process.

6. The apparatus as recited in claim 1 wherein the recovery mechanism is configured to convert a message request from a normal message request into a special message request by setting a recovery attribute bit.

7. The apparatus as recited in claim 1 wherein the recovery mechanism is configured to convey each special message request to the first stage, and wherein the first stage is configured to identify said each special message request in the first set of records.

8. The apparatus as recited in claim 7 wherein the first stage is configured to determine whether a message request is a normal message request or a special message request, and wherein the first stage is configured to send each special message request to the second stage without determining whether the special message request is a duplicate request.

9. The apparatus as recited in claim 1 wherein the second stage is configured to identify the corresponding request as a failed request in a failure log.

10. The apparatus as recited in claim 1 wherein the first set of records are stored in a first database.

11. The apparatus as recited in claim 1 wherein the second set of records are stored in a second database.

12. A transaction processing system comprising:

a message processor;

one or more processors; and

a storage device storing program instructions executable by the one or more processors to implement a message brokering mechanism including;

a first stage operable to interface with a message source, wherein the first stage is configured to maintain a first set of records identifying message requests received from the message source and message responses sent to the message source;

a second stage operable to interface with the message processor, wherein the second stage is configured to maintain a second set of records identifying message requests sent to the message processor and message responses received from the message processor; and

a recovery mechanism;

wherein the first stage is configured to determine whether a normal message request received from the message source is a duplicate request and, if the normal message request is not a duplicate request, to dispatch the normal message request to the second stage, and, if the normal message request is a duplicate request, to send a message response to the message source without dispatching the normal message request to the second stage;

wherein, in response to receiving the normal message request, the second stage is configured to send the normal message request to the message processor and, if a message response is received from the message processor, to dispatch the message response to the first stage for sending to the message source;

wherein, in response to receiving a recovery process activation message, the recovery mechanism is configured to access each of the first and second sets of records to identify those message requests for which a corresponding message response is not included indicating that the message request has been processed and to convert each such message request into a corresponding special message request; and

wherein, in response to receiving a given special message request, the second stage is configured to send a corresponding request to the message processor and to start a timer process and, if a response is not received from the message processor within a designated time period as dictated by the timer process, to identify the corresponding request as a failed request.

13. The system as recited in claim 12 wherein, in response to determining that the normal message request is a duplicate request, the first stage is further configured to determine whether an existing message response is included in the first set of records.

14. The system as recited in claim 13 wherein, in response to determining that an existing message response is included in the first set of records, the first stage is further configured to send the existing message response to the message source.

15. The system as recited in claim 13 wherein, in response to determining that an existing message response is not included in the first set of records, the first stage is further configured to send an in progress message response to the message source.

16. The system as recited in claim 12 wherein, in response to receiving the given special message request, the second stage is configured to determine whether an existing response message to the given special message request is included in the second set of records and, if so, to send the existing response to the first stage for forwarding to the message source instead of sending the corresponding request to the message processor and starting the timer process.

17. The system as recited in claim 12 wherein the recovery mechanism is configured to convert a message request from a normal message request into a special message request by setting a recovery attribute bit.

18. The system as recited in claim 12 wherein the recovery mechanism is configured to convey each special message request to the first stage, and wherein the first stage is configured to identify said each special message request in the first set of records.

19. The system as recited in claim 18 wherein the first stage is configured to determine whether a message request is a normal message request or a special message request, and wherein the first stage is configured to send each special message request to the second stage without determining whether the special message request is a duplicate request.

20. The system as recited in claim 12 wherein the second stage is configured to identify the corresponding request as a failed request in a failure log.

21. The system as recited in claim 12 wherein the first set of records are stored in a first database.

22. The system as recited in claim 12 wherein the second set of records are stored in a second database.

23. A storage medium storing program instructions executable by a computing device to implement a message brokering mechanism including:

a first stage operable to interface with a message source, wherein the first stage is configured to maintain a first set of records identifying message requests received from the message source and message responses sent to the message source;

a second stage operable to interface with a message processor, wherein the second stage is configured to maintain a second set of records identifying message requests sent to the message processor and message responses received from the message processor; and

a recovery mechanism;

wherein the first stage is configured to determine whether a normal message request received from the message source is a duplicate request and, if the normal message request is not a duplicate request, to dispatch the normal message request to the second stage, and, if the normal message request is a duplicate request, to send a message response to the message source without dispatching the normal message request to the second stage;

wherein, in response to receiving the normal message request, the second stage is configured to send the normal message request to the message processor and, if a message response is received from the message processor, to dispatch the message response to the first stage for sending to the message source;

wherein, in response to receiving a recovery process activation message, the recovery mechanism is configured to access each of the first and second sets of records to identify those message requests for which a corresponding message response is not included indicating that the message request has been processed and to convert each such message request into a corresponding special message request; and

wherein, in response to receiving a given special message request, the second stage is configured to send a corresponding request to the message processor and to start a timer process and, if a response is not received from the message processor within a designated time period as dictated by the timer process, to identify the corresponding request as a failed request.

24. The storage medium as recited in claim 23 wherein, in response to determining that the normal message request is a duplicate request, the first stage is further configured to determine whether an existing message response is included in the first set of records.

25. The storage medium as recited in claim 24 wherein, in response to determining that an existing message response is included in the first set of records, the first stage is further configured to send the existing message response to the message source.

26. The storage medium as recited in claim 24 wherein, in response to determining that an existing message response is not included in the first set of records, the first stage is further configured to send an in progress message response to the message source.

27. The storage medium as recited in claim 23 wherein, in response to receiving the given special message request, the second stage is configured to determine whether an existing response message to the given special message request is included in the second set of records and, if so, to send the existing response to the first stage for forwarding to the message source instead of sending the corresponding request to the message processor and starting the timer process.

28. The storage medium as recited in claim 23 wherein the recovery mechanism is configured to convert a message request from a normal message request into a special message request by setting a recovery attribute bit.

29. The storage medium as recited in claim 23 wherein the recovery mechanism is configured to convey each special message request to the first stage, and wherein the first stage is configured to identify said each special message request in the first set of records.

30. The storage medium as recited in claim 23 wherein the first stage is configured to determine whether a message request is a normal message request or a special message request, and wherein the first stage is configured to send each special message request to the second stage without determining whether the special message request is a duplicate request.

31. The storage medium as recited in claim 23 wherein the second stage is configured to identify the corresponding request as a failed request in a failure log.

32. The storage medium as recited in claim 23 wherein the first set of records are stored in a first database.

33. The storage medium as recited in claim 23 wherein the second set of records are stored in a second database.