Systems and methods for maintaining transactional persistence

• US 7,356,532 B2
• Filed: 02/16/2005
• Issued: 04/08/2008
• Est. Priority Date: 06/27/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Dalal, Sanjay, Wiser, David
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US11/058,888
• Publication Number:
  US 20050149526A1
• Time in Patent Office: 1,147 Days
• Field of Search: 707/10, 707/101, 707/102, 707/103.R, 707/8, 707/9, 705/26, 714/20
• US Class Current: 707/703
• CPC Class Codes: G06F 2209/523 Mode
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Messages between trading partners can be processed persistently using a persistence framework, which can include a transaction manager, a locking manager, and a logging mechanism. A transaction manager can initiate a transaction for a request, and can enlist and modify any object or resource useful in processing the request. A locking manager can lock any of these objects, using inflated and/or individual locks, to prevent other resources or transactions from accessing the object during the transaction. A logging component can track any modifications of the object, while a transaction manager can manage state for the object.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A method for persistently processing a request, comprising:

initiating a transaction to process a request using a transaction manager;

enlisting any object useful in processing the request;

locking any object enlisted by the transaction manager;

modifying the object in order to process the request; and

logging the modifications to the object;

wherein

an inflated lock is initially placed on objects that potentially are part of the transaction and wherein a thin lock is placed on enlisted objects, further comprising committing the transaction when the request is successfully processed.

2. A method according to claim 1, further comprising:

storing any modifications to the object during the processing of the request to a database after the request has been processed.

3. A method according to claim 1, further comprising:

sending the request to a message queue after processing the request.

4. A method according to claim 1, further comprising:

committing the transaction if the request is successfully processed.

5. A method according to claim 1, further comprising:

undoing any logged modifications to the object when the request is not successfully processed.

6. A method according to claim 1, further comprising:

unlocking any locked object after the request is processed.

7. A computer-readable storage medium, comprising:

means for initiating a transaction to process a request using a transaction manager;

means for enlisting any object useful in processing the request;

means for locking any object enlisted by the transaction manager;

means for modifying the object in order to process the request; and

means for logging the modifications to the object;

wherein

an inflated lock is initially placed on objects that potentially are part of the transaction and wherein a thin lock is placed on enlisted objects, further comprising committing the transaction when the request is successfully processed.

8. A computer program product for execution by a server computer for persistently processing a request, the computer program product stored on a computer readable storage medium, comprising:

computer code to initiate a transaction to process a request using a transaction manager;

computer code to enlist any object useful in processing the request;

computer code to lock any object enlisted by the transaction manager;

computer code to modify the object in order to process the request; and

computer code to log the modifications to the object;

wherein

an inflated lock is initially placed on objects that potentially are part of the transaction and wherein a thin lock is placed on enlisted objects, further comprising committing the transaction when the request is successfully processed.

9. A computer-based system for persistently processing a request, comprising:

means for initiating a transaction to process a request using a transaction manager;

means for enlisting any object useful in processing the request;

means for locking any object enlisted by the transaction manager;

means for modifying the object in order to process the request; and

means for logging the modifications to the object;

wherein

an inflated lock is initially placed on objects that potentially are part of the transaction and wherein a thin lock is placed on enlisted objects, further comprising committing the transaction when the request is successfully processed.

10. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

initiate a transaction to process a request using a transaction manager;

enlist any object useful in processing the request;

lock any object enlisted by the transaction manager;

modify the object in order to process the request; and

log the modifications to the object;

wherein

an inflated lock is initially placed on objects that potentially are part of the transaction and wherein a thin lock is placed on enlisted objects, further comprising committing the transaction when the request is successfully processed.