Method and apparatus for partitioning of managed state for a Java based application

• US 7,246,345 B1
• Filed: 04/02/2001
• Issued: 07/17/2007
• Est. Priority Date: 04/02/2001
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Sharma, Rahul, Krishnan, Sanjeev, Matena, Vladimir, Mortazavi, Masood
• Primary Examiner(s): Dam; Tuan
• Assistant Examiner(s): Pham; Chrystine
• Application Number:
  US09/825,249
• Time in Patent Office: 2,297 Days
• Field of Search: None
• US Class Current: 717/120
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

A method is disclosed for partitioning a managed state for a Java based application. The application developer is allowed to associate individual entity beans with a particular state management type. Then, during execution, a plurality of state objects are provided, where each state object stores a state of a corresponding entity bean object within the memory address space of a Java server process. Further, each state object is associated with the state management type of the corresponding entity bean object. In this manner, state management is provided for each entity bean object based on the associated state management type using a corresponding state object. The state management type can be a memory replicated state management type, a disk replicated state management type, a non-replicated state manage type.

Claims

1. A method for managing container-managed state for a Java based application, comprising the operations of:

classifying individual entity bean objects according to a particular state management type, the state management type being one of a recoverable state or a non-recoverable state, the recoverable state being one of a memory replicated state management type and a disk replicated state management type;

storing a plurality of state objects, each state object storing a state of a corresponding entity bean object within a memory address space of a Java server process, wherein each state object is associated with the state management type of the corresponding entity bean object; and

providing state management for each entity bean object using a state object associated with the state management type corresponding to the respective entity bean object, the providing state management being based separately on each different state management type and on those state objects corresponding to the different state management type, the providing state management comprising replicating each one of the plurality of state objects in a state server, a different one of the state servers being dedicated to a particular one of the state management types, a different one of the state servers being provided for each different recoverable state management type, each of the state servers being separate from the memory address space of the Java server process.

2. A method as recited in claim 1, further comprising the operation of grouping the state objects based on the type of state management to which the corresponding entity bean object is classified.

3. A method as recited in claim 2, wherein the state management type into which a group of state objects are grouped identifies a policy for replication of the group of state objects to the dedicated state server that is dedicated to the different state management type corresponding to the group.

4. A method as recited in claim 2, wherein the state management type identifies a policy for migration of a state object from one server process to another server process.

5. A method as recited in claim 1, further comprising the operation of managing checkpoints using the state objects.

6. A method as recited in claim 1, further comprising the operation of performing lock management using the state objects.

7. A method as recited in claim 1, wherein the operation of providing state management further comprises replicating one of the plurality of state objects that is associated with the memory replicated state management type of the corresponding entity bean object, the last-mentioned replicating being in the state server dedicated to the memory replicated state management type that is separate from the memory address space of the Java server process.

8. A method for managing container-managed state for a Java application, comprising the operations of:

partitioning individual entity bean objects of the Java application into state partitions, wherein the state partitions manage concurrency for the Java application, the partitioning being by storing state of each particular entity bean object in a state object dedicated to a state management type corresponding to the state management type of the particular entity bean object, the state management types being one of a recoverable state or a non-recoverable state, the recoverable state being one of a memory replicated state management type and a disk replicated state management type, each state object storing the state of a corresponding entity bean object within a memory address space of a Java server process;

classifying individual state objects within each state partition using state management units, wherein each particular state management unit is a collection of the state objects corresponding to one particular state management type for recoverable and migration capable state of the respective corresponding particular entity bean objects; and

replicating each particular state management unit in one of a plurality of state servers according to the particular state management type that corresponds to the particular state objects classified in the particular state management unit, each of the state servers being separate from the memory address space of the Java server process.

9. A method as recited in claim 8, further comprising the operation of using a control module to manage dynamic partitioning of the state of the application via the state partitions and the state management units.

10. A method as recited in claim 9, wherein the state partitions and state management units are modular.

11. A method as recited in claim 10, wherein additional state management types for the state management units can be defined.

12. A method as recited in claim 11, wherein each state partition serializes transactions for entity bean objects within a particular state partition.

13. A method as recited in claim 12, wherein each state partition allows only one concurrent transaction to be performed on the entity bean objects within the particular state partition during a given time period.

14. A method as recited in claim 8, wherein the operation of replicating each particular state management unit further comprises replicating the state management unit that collects the state objects corresponding to the memory replicated state management type of the corresponding entity bean objects, the last-mentioned replicating being in the state server for the memory replicated state management type that is separate from the memory address space of the Java server process.

15. A system for managing container-managed state for a Java based application, comprising:

an application having a plurality of entity bean objects, each entity bean object comprising a state management type, the state management type being one of a recoverable state or a non-recoverable state, the recoverable state being one of a memory replicated state management type and a disk replicated state management type;

a plurality of state objects, each state object storing a state of a corresponding entity bean object within a memory address space of a Java server process, wherein each state object is associated with a particular state management type of the corresponding entity bean object;

a plurality of state management units that classify the state objects, a particular state object being classified into a particular state management unit based on the particular state management type of the corresponding entity bean object, wherein the state management units facilitate state management for each entity bean object;

a state server dedicated to each state management type, the state management type identifying a policy for replication of a state object to a state server dedicated to a particular state management type and a policy for migration of a state object from one server process to another server process, each of the state servers being separate from the memory address space of the Java server process; and

a replicated state manager configured to replicate a particular state management unit to the state server that is dedicated to the particular state management type of the particular state object that is classified into the particular state management unit to be replicated.

16. A system as recited in claim 15, wherein the entity bean objects of the application are partitioned into state partitions during pre-deployment.

17. A system as recited in claim 16, further comprising a repository that maintains state partition specifications for the state partitions.

18. A system as recited in claim 17, wherein the repository manages replication and migration of state of the Java application during runtime.

19. A system as recited in claim 15, wherein the replicated state manager is further configured to replicate a particular state object from the one server process to the other server process according to the policy for migration.

20. A system as recited in claim 15, wherein the replicated state manager is further configured to replicate the particular state management unit that has classified the state objects associated with the memory replicated state management type, the replicated state manager replicating the last-mentioned particular state management unit to the state server that is dedicated to the memory replicated state management type, the state server that is dedicated to the memory replicated state management type being separate from the memory address space of the Java server process.