Inserting new transactions into a transaction stream

• US 7,996,401 B2
• Filed: 05/31/2007
• Issued: 08/09/2011
• Est. Priority Date: 05/31/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wisniewski, Robert, Newport, William Thomas, Stecher, John Joseph
• Primary Examiner(s): Robinson; Greta L
• Assistant Examiner(s): Chang; Jeffrey
• Application Number:
  US11/755,809
• Publication Number:
  US 20080301682A1
• Time in Patent Office: 1,531 Days
• Field of Search: 707/736
• US Class Current: 707/736
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

In an embodiment, a selection of an original transaction is received. In response to the selection of the original transaction, a call stack of the application that sends the original transaction during a learn mode of the application is saved. A specification of a new transaction and a location of the new transaction with respect to the original transaction in an transaction stream is received. During a production mode of the application, the original transaction is received from the application. A determination is made that the call stack of the application during the production mode matches the saved call stack of the application during the learn mode. In response to the determination, the new transaction is inserted at the location into a transaction stream that is sent to a database.

Claims

1. A method comprising:

receiving an original transaction from an application during a production mode of the application;

determining whether a call stack of the application during the production mode matches a call stack of the application during a learn mode;

if the call stack of the application during the production mode matches the call stack of the application during the learn mode, inserting a new transaction in a transaction stream sent to a database and sending a result of the new transaction to the application; and

if the call stack of the application during the production mode does not match the call stack of the application during the learn mode, sending the original transaction to the database without sending the new transaction to the database and sending a result of the original transaction to the application.

2. The method of claim 1, further comprising:

receiving a selection of the original transaction; and

in response to receiving the selection of the original transaction, saving the call stack of the application that sends the original transaction during the learn mode of the application.

3. The method of claim 2, further comprising:

receiving a specification of the new transaction and a location of the new transaction with respect to the original transaction, wherein the inserting inserts the new transaction at the location in the transaction stream.

4. The method of claim 3, wherein the location is before the original transaction in the transaction stream.

5. The method of claim 3, wherein the location is after the original transaction in the transaction stream.

6. The method of claim 3, wherein the location specifies replacing the original transaction in the transaction stream.

7. The method of claim 3, wherein the determining further comprises:

determining whether method names in the call stacks of the learn mode and the production mode match.

8. A storage medium encoded with instructions, wherein the instructions when executed comprise:

receiving a selection of an original transaction;

in response to receiving the selection of the original transaction, saving a call stack of the application that sends the original transaction during a learn mode of the application;

receiving the original transaction from an application during a production mode of the application;

determining whether a call stack of the application during the production mode matches a call stack of the application during a learn mode;

if the call stack of the application during the production mode matches the call stack of the application during the learn mode, inserting a new transaction in a transaction stream sent to a database and sending a result of the new transaction to the application; and

if the call stack of the application during the production mode does not match the call stack of the application during the learn mode, sending the original transaction to the database without sending the new transaction to the database and sending a result of the original transaction to the application.

9. The storage medium of claim 8, further comprising:

receiving a specification of the new transaction and a location of the new transaction with respect to the original transaction, wherein the inserting inserts the new transaction at the location in the transaction stream.

10. The storage medium of claim 9, wherein the location is before the original transaction in the transaction stream.

11. The storage medium of claim 9, wherein the location is after the original transaction in the transaction stream.

12. The storage medium of claim 9, wherein the location specifies replacing the original transaction in the transaction stream.

13. The storage medium of claim 9, wherein the determining further comprises:

determining whether method names in the call stacks of the learn mode and the production mode match.

14. The storage medium of claim 13, wherein the determining further comprises:

determining whether a call order of the method names in the call stacks of the learn mode and the production mode match.

15. The storage medium of claim 13, wherein the determining further comprises:

determining whether return addresses in the call stacks of the learn mode and the production mode match.

16. A computer system comprising:

a processor; and

memory connected to the processor, wherein the memory encodes instructions that when executed by the processor comprise;

receiving a selection of an original transaction,

in response to receiving the selection of the original transaction, saving a call stack of the application that sends the original transaction during a learn mode of the application,

receiving a specification of a new transaction and a location of the new transaction with respect to the original transaction,

receiving the original transaction from an application during a production mode of the application,

determining whether a call stack of the application during the production mode matches a call stack of the application during a learn mode,

if the call stack of the application during the production mode matches the call stack of the application during the learn mode, inserting a new transaction in a transaction stream sent to a database and sending a result of the new transaction to the application, and

if the call stack of the application during the production mode does not match the call stack of the application during the learn mode, sending the original transaction to the database without sending the new transaction to the database and sending a result of the original transaction to the application.

17. The computer system of claim 16, wherein the determining further comprises:

determining whether method names and a call order of the method names in the call stacks of the learn mode and the production mode match.

18. The computer system of claim 17, wherein the determining further comprises:

determining whether return addresses in the call stacks of the learn mode and the production mode match.

19. The computer system of claim 17, wherein the determining further comprises:

determining whether parameters in the call stacks of the learn mode and the production mode match.

20. The computer system of claim 17, wherein the determining further comprises:

determining whether local variables in the call stacks of the learn mode and the production mode match.