Transaction manager freezing

• US 7,640,545 B2
• Filed: 07/14/2003
• Issued: 12/29/2009
• Est. Priority Date: 07/14/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: K, Venugopal Rao, Kumar, Ajay, Dutt, Bala, Kannan, Srinivasan, Bhogi, Sankara R.
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): Truong; Camquy
• Application Number:
  US10/618,828
• Publication Number:
  US 20050015425A1
• Time in Patent Office: 2,360 Days
• Field of Search: 718/101, 718/106, 707/3, 707/8, 711/147, 705/40, 705/70
• US Class Current: 718/101
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A transaction manager may be paused so that the transactions it manages are prevented from making transaction state changes. While the transaction manager is paused, the transactions that the transaction manager is executing may not be allowed to complete. A transaction manager may be configured to obtain permission from a transaction freeze manager in order to transition the state of a transaction. The transaction freeze manager may function as a read/write lock manager controlling locks on a transaction freeze object. In servicing a transaction state transition request, the transaction freeze manager may grant the transaction manager a read lock on the transaction freeze object. In servicing a transaction manager pause request, the transaction freeze manager may grant an administrative entity a write lock on the transaction freeze object.

Claims

1. A system, comprising:

one or more processors;

memory coupled to the one or more processors and configured to store program instructions executable by the one or more processors to implement a transaction manager, wherein the transaction manager is configured to;

manage a plurality of transactions initiated by one or more applications, wherein each transaction comprises a plurality of operations to one or more data sources that are required to be committed to the one or more data sources atomically for each respective transaction;

pause currently executing ones of the plurality of transactions managed by the transaction manager in response to a pause request to pause the transaction manager, wherein while paused, the transaction manager does not allow any of the plurality of transactions managed by the transaction manager to complete;

allow the execution of each of the plurality of transactions managed by the transaction manager within a respective current state while the transaction manager is paused; and

resume execution of the paused ones of the plurality of transactions managed by the transaction manager in response to a resume request.

2. The system as recited in claim 1, wherein the transaction manager is configured to change the state of each of the plurality of transaction managed by the transaction manager.

3. The system as recited in claim 2, wherein the transaction manager is configured to request permission to change the state of each of the plurality of transactions managed by the transaction manager prior to changing the state of each respective transaction.

4. The system as recited in claim 3, wherein the transaction manager is configured to wait for permission to change the state of each of the plurality of transactions managed by the transaction manager.

5. The system as recited in claim 1, wherein the transaction manager is configured to prohibit a change of state of each of the plurality of transactions managed by the transaction manager while the transaction manager is paused.

6. The system as recited in claim 1, wherein the system is configured to continue the execution of the one or more applications while the transaction manager is paused, except for changing of transaction states.

7. The system as recited in claim 1, wherein while the transaction manager is paused, the system is configured to perform operations on one or more individual transactions.

8. The system as recited in claim 7, wherein the operations comprise one or more from the following:

rollback, abort, partial rollback, add/remove participant, and commit.

9. The system as recited in claim 1, wherein one or more of the transactions are local transactions.

10. The system as recited in claim 9, wherein while paused, the transaction manager is not allowed to change the state of the one or more transactions to the committing state.

11. The system as recited in claim 1, wherein one or more of the transactions are global transactions.

12. The system as recited in claim 11, wherein while paused, the transaction manager is not allowed to change the state of the one or more transactions to the preparing state nor to the committing state.

13. A system, comprising:

one or more processors; and

memory coupled to the one or more processors and configured to store program instructions executable by the one or more processors to implement one or more application servers, wherein each one or more application servers is configured to;

run one or more applications each configured to initiate one or more transactions, wherein each of the one or more transactions comprises a plurality of operations to one or more data sources that are required to be committed to the one or more data sources atomically for the transaction; and

provide one or more transaction managers configured to manage the one or more transactions initiated by the one or more applications, wherein one of the one or more transaction managers is configured to;

pause one or more of the one or more currently executing transactions in response to a pause request, wherein the one of the one or more transaction managers does not allow the one or more transactions that have been paused to complete while paused;

allow the execution of the one or more transactions that have been paused within a respective current state while paused; and

resume one or more of the one or more transactions that have been paused in response to a resume request.

14. A computer-implemented method, comprising:

using one or more computers to perform;

generating a request to pause a transaction manager;

pausing the transaction manager in response to said request, wherein while the transaction manager is paused, transactions currently executing and managed by the transaction manager are prohibited from completing, wherein the transactions are initiated by one or more applications;

allowing the execution of the transactions managed by the transaction manager within a respective current state while the transaction manager is paused;

generating a request to resume the transaction manager; and

resuming the transaction manager in response to said request, wherein when the transaction manager is resumed, paused transactions managed by the transaction manager are allowed to complete, wherein each transaction managed by the transaction manager comprises a plurality of operations to one or more data sources that are required to be committed to the one or more data sources atomically for each respective transaction.

15. The method as recited in claim 14, wherein said pausing comprises prohibiting the transaction manager from changing the state of the transactions, wherein the transaction manager attempts to perform a state change on a transaction in response to input to the transaction manager.

16. The method as recited in claim 15, wherein the input comprises notification that an application has initiated a transaction.

17. The method as recited in claim 16, wherein said state change comprises a change from a nonexistent state to an active state.

18. The method as recited in claim 15, wherein the input comprises notification that an application has executed a commit transaction command.

19. The method as recited in claim 18, wherein said state change comprises a change from an active state to a preparing state.

20. The method as recited in claim 15, wherein the input comprises notification that all participants are prepared commit the transaction.

21. The method as recited in claim 20, wherein said state change comprises a change from a preparing state to a committing state.

22. The method as recited in claim 15, wherein the input comprises notification that all participants have committed the transaction.

23. The method as recited in claim 22, wherein said state change comprises a change from a committing state to a nonexistent state.

24. The method as recited in claim 15, further comprising, while the transaction manager is paused, continuing to support the execution of the one or more applications, except for the changing of transaction states.

25. A computer-readable storage medium storing program instructions, wherein the program instructions are computer-executable to:

generate a request to pause a transaction manager;

pause a plurality of transactions managed by the transaction manager in response to said request to pause the transaction manager, wherein while the transaction manager is paused, the plurality of currently executing transactions managed by the transaction manager are prohibited from completing, wherein the plurality of transactions are initiated by one or more applications, wherein each transaction comprises a plurality of operations to one or more data sources that are required to be committed to the one or more data sources atomically for each respective transaction;

allow the execution of each of the plurality of transactions managed by the transaction manager within a respective current state while the transaction manager is paused;

generate a request to resume the transaction manager; and

resume the plurality of transactions managed by the transaction manager in response to said resume request, wherein when the transaction manager is resumed, the plurality of paused transactions managed by the transaction manager are allowed to complete.

26. The computer-readable storage medium as recited in claim 25, wherein the program instructions are computer-executable to pause the transaction manager by prohibiting the transaction manager from changing the state of any of the plurality of transactions managed by the transaction manager, wherein the transaction manager attempts to perform a state change on a transaction in response to input to the transaction manager.

27. The computer-readable storage medium as recited in claim 26, wherein the input comprises notification that an application has initiated a transaction.

28. The computer-readable storage medium as recited in claim 27, wherein said state change comprises a change from a nonexistent state to an active state.

29. The computer-readable storage medium as recited in claim 26, wherein the input comprises notification that an application has executed a commit transaction command.

30. The computer-readable storage medium as recited in claim 29, wherein said state change comprises a change from an active state to a preparing state.

31. The computer-readable storage medium as recited in claim 26, wherein the input comprises notification that all participants are prepared commit the transaction.

32. The computer-readable storage medium as recited in claim 31, wherein said state change comprises a change from a preparing state to a committing state.

33. The computer-readable storage medium as recited in claim 26, wherein the input comprises notification that all participants have committed the transaction.

34. The computer-readable storage medium as recited in claim 33, wherein said state change comprises a change from a committing state to a nonexistent state.

35. The computer-readable storage medium as recited in claim 26, wherein the program instructions are computer-executable to, while the plurality of transactions managed by the transaction manager is are paused, continue to support the execution of the one or more applications, except for the changing of transaction states.