JAVA VIRTUAL MACHINE HAVING INTEGRATED TRANSACTION MANAGEMENT SYSTEM

• US 20090276658A1
• Filed: 04/30/2009
• Published: 11/05/2009
• Est. Priority Date: 05/01/2008
• Status: Active Grant

• Current Assignee: Cloud Software Group
• Original Assignee: Kabira Technologies, Inc. (Cloud Software Group)
• Inventors: ZANG, Xiguang, PILE, Jonathon C., SIFTER, Daniel J., PHILLIPS, Mark, STONE, David, LIND, Otto, SARMIENTO, Ramiro
• Granted Patent: US 8,219,852 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

A computing system is configured to deploy a JAVA application for execution in a distributed manner. The computing system includes a plurality of computing nodes including a domain manager node, the plurality of computing nodes forming a computing domain configured as an administrative grouping of the nodes administered by the domain manager node. The domain manager node is configured to provide, to each of the computing nodes, a main portion of the JAVA application. The main portion defines, for each computing node, a portion of the behavior of the JAVA application to be accomplished by that computing node. Furthermore, each computing node is configured to receive at least one class file having classes appropriate for the portion of the behavior of the JAVA application defined, by the main portion, to be accomplished by that computing node.

Claims

1. A computing system configured to deploy a JAVA application for execution in a distributed manner, the computing system comprising:

a plurality of computing nodes including a domain manager node, the plurality of computing nodes forming a computing domain configured as an administrative grouping of the nodes administered by the domain manager node;

wherein

the domain manager node is configured to provide, to each of the computing nodes, a main portion of the JAVA application;

the main portion defines, for each computing node, a portion of the behavior of the JAVA application to be accomplished by that computing node; and

each computing node is configured to receive at least one class file having classes appropriate for the portion of the behavior of the JAVA application defined, by the main portion, to be accomplished by that computing node.

2. The computing system of claim 1, wherein:

the computing system is configured such that transactions on objects of the JAVA application may be distributed across multiple ones of the computing nodes.

3. The computing system of claim 2, wherein:

the transactions on objects of the JAVA application being distributed across multiple ones of the computing nodes includes maintaining, across the multiples ones of the computing nodes and in a distributed manner, objects that are indicative of a transactional state of the JAVA application.

4. The computing system of claim 2, wherein:

the objects are distributed across multiple ones of the computing nodes so as to maintain a state of the objects in a fault-tolerant manner.

5. The computing system of claim 4, wherein:

distributing the objects across multiple ones of the computing nodes includes replicating each of at least some of the objects from a primary computing node for that object to at least one secondary computing node for that object.

6. The computing system of claim 5, wherein:

the system is configured such that, when one of the computing nodes becomes inoperable, at least one other computing node has access to a state of the objects for which that inoperable computing node was primary, in order to continue to accomplish the behavior of the JAVA application in a fault tolerant manner, without the inoperable computing node.

7. The computing system of claim 1, wherein the computing system is further configured to:

execute a deployment tool, the deployment tool configured to define, to the domain manager, which computing nodes form the computing domain.

8. The computing system of claim 7, wherein:

the deployment tool is configured to dynamically change the domain definition to add a new computing node to the computing domain while the computing nodes of the domain are currently executing the JAVA application; and

data required by a portion of the behavior of the JAVA application defined, by the main portion, to be accomplished by the new computing node is accessible via at least one object managed by computing nodes of the domain other than the new computing node.

9. A method of deploying a JAVA application for execution in a distributed manner, comprising:

providing a plurality of computing nodes including a domain manager node, the plurality of computing nodes forming a computing domain configured as an administrative grouping of the nodes administered by the domain manager node;

providing, by the domain manager node, to each of the computing nodes, a main portion of the JAVA application, wherein the main portion defines, for each computing node, a portion of the behavior of the JAVA application to be accomplished by that computing node; and

receiving by each computing node at least one class file having classes appropriate for the portion of the behavior of the JAVA application defined, by the main portion, to be accomplished by that computing node.

10. The method of claim 9, wherein:

the computing system is configured such that transactions on objects of the JAVA application may be distributed across multiple ones of the computing nodes.

11. The method of claim 10, wherein:

maintaining, across the multiples ones of the computing nodes and in a distributed manner, objects that are indicative of a transactional state of the JAVA application, to distribute the transactions on objects of the JAVA application across multiple ones of the computing nodes.

12. The method system of claim 9, wherein:

the objects are distributed across multiple ones of the computing nodes so as to maintain a state of the objects in a fault-tolerant manner.

13. The method of claim 12, wherein:

distributing the objects across multiple ones of the computing nodes includes replicating each of at least some of the objects from a primary computing node for that object to at least one secondary computing node for that object.

14. The method of claim 13, wherein:

the computing system is configured such that, when one of the computing nodes becomes inoperable, at least one other computing node has access to a state of the objects for which that inoperable computing node was primary, in order to continue to accomplish the behavior of the JAVA application in a fault tolerant manner, without the inoperable computing node.

15. The method of claim 9, wherein the computing system is further comprising:

executing a deployment tool to define, to the domain manager, which computing nodes form the computing domain.

16. The method of claim 15, further comprising:

configuring the deployment tool to dynamically change the domain definition to add a new computing node to the computing domain while the computing nodes of the domain are currently executing the JAVA application; and

wherein data required by a portion of the behavior of the JAVA application defined, by the main portion, to be accomplished by the new computing node is accessible via at least one object managed by computing nodes of the domain other than the new computing node.