# US 2012/0254867 A1 · Java virtual machine having integrated transaction management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254867 A1
- Document ID: US20120254867A1
- Status: Published application
- Kind: A1
- Application number: 13/464,814
- Filed: 2012-05-04
- Published: 2012-10-04
- Earliest claimed: 2008-05-01
- Assignees: Kabira Technologies, Inc.
- Inventors: Otto LIND; Jonathon C. Pile; Ramiro Sarmiento; Daniel J. Sifter; David Stone; Xiguang Zang; Mark Phillips
- Web page: https://patentgrep.com/patent/US20120254867A1

## CPC

- G06F 9/466: {Transaction processing}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 1

A computing system configured to deploy an application in a platform independent programming language 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;
a virtual machine integration layer integrating at least one Virtual Machine (VM) with a transaction processing platform that is transparent to the platform independent language; and
the domain manager node coordinating the deployment and distribution of distributed transactional applications to the computing domain, the domain manager being configured to provide, to each of the computing nodes, a first portion of the application where the first portion defines, for each computing node, a portion of the behavior of the application to be accomplished by that computing node and each computing node is configured to receive from the domain manager at least one executable file for the portion of the behavior of the application defined, by the first portion, to be accomplished by that computing node; and
the integration layer includes at least one of service adaptors and transaction bindings to support user-defined business logic being executed by the one or more virtual machines employing the transaction processing features of the underlying transaction processing platform, wherein distributed applications for transactional processing on one or more virtual machines are transparently distributed and managed.

### Claim 2

A method of deploying an application in a platform independent programming language 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 wherein the domain manager coordinates the deployment and distribution of transactional applications to the computing domain, the domain manager;
providing a virtual machine integration layer integrating at least one Virtual Machine (VM) with a transaction processing platform that is transparent to the platform independent language;
providing, by the domain manager node, to each of the computing nodes, a first portion of the application, wherein the first portion defines, for each computing node, a portion of the behavior of the application to be accomplished by that computing node;
receiving by each computing node at least one executable file appropriate for the portion of the behavior of the application defined, by the first portion, to be accomplished by that computing node; and
providing at least one of service adaptors and transaction bindings to support user-defined business logic being executed by virtual machine employing the transaction processing features of the underlying transaction processing platform;
wherein distributed applications for transaction processing on one or more virtual machines are transparently distributed and managed.

### Claim 3 (depends on 2)

The method of claim 2, wherein a user-defined business logic specified in the platform independent language is executed on a Virtual Machine and transparently accesses transaction processing features of the transactional processing platform.

### Claim 4

A computer system configured to deploy an application in a platform independent programming language 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;
a virtual machine integration layer integrating at least one Virtual Machine (VM) with a transaction processing platform that is transparent to the platform independent language;
the domain manager node coordinating the deployment and distribution of distributed transactional applications to the computing domain, the domain manager is configured to provide, to each of the computing nodes, a first portion of the application where the first portion defines, for each computing node, a portion of the behavior of the application to be accomplished by that computing node and each computing node is configured to receive from the domain manager at least one executable file for the portion of the behavior of the application defined, by the first portion, to be accomplished by that computing node; and
transaction bindings and a virtual machine interpreter supporting user-defined business logic being executed by the one or more virtual machines employing the transaction processing features of the underlying transaction processing platform and the computing system is configured such that transactions on objects of the application may be distributed across multiple ones of the computing nodes;
wherein distributed applications for transactional processing on one or more virtual machines are transparently distributed and managed.

### Claim 5 (depends on 4)

The computer system of claim 4, wherein:
the transactions on objects of the 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, transactional objects that are indicative of a transactional state of the application.

### Claim 6 (depends on 4)

The computer system of claim 4, wherein:
the transactional objects are distributed across multiple ones of the computing nodes so as to maintain a state of the transactional objects in a fault-tolerant manner.

### Claim 7 (depends on 6)

The computer system of claim 6, wherein:
distributing the objects across multiple ones of the computing nodes includes replicating each of at least some of the transactional objects from an active computing node for that object to at least one replica computing node for that object.

### Claim 8 (depends on 7)

The computer system of claim 7, 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 transactional objects for which that inoperable computing node was active, in order to continue to accomplish the behavior of the application in a fault tolerant manner, without the inoperable computing node.

### Claim 9 (depends on 4)

The computer system of claim 4, 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.

### Claim 10 (depends on 9)

The computer system of claim 9, 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 application; and
data required by a portion of the behavior of the application defined, by the first portion, to be accomplished by the new computing node is accessible via at least one transactional object managed by computing nodes of the domain other than the new computing node.

### Claim 11 (depends on 4)

The computer system of claim 4, further comprising location transparent distribution including location transparency for managed objects.

### Claim 12 (depends on 11)

The computer system of claim 11, wherein the location transparent distribution includes providing for each managed object a distributed reference containing the location where the object was created.

### Claim 13 (depends on 11)

The computer system of claim 11, wherein the location transparent distribution comprises location discovery for runtime discovery of location information.

### Claim 14 (depends on 4)

The computer system of claim 4, wherein a new node joins a domain that is currently executing an application, the application is deployed to the new node transparently.

### Claim 15 (depends on 4)

The computer system of claim 4, wherein a new node joins a domain that is currently executing an application, the application is deployed to the new node transparently.

### Claim 16 (depends on 4)

The computer system of claim 4, wherein code of the platform independent programming language of the application transparently executes with transaction processing semantics.

### Claim 17 (depends on 4)

The computer system of claim 4, wherein a user-defined business logic specified in the platform independent language is executed on a Virtual Machine and transparently accesses transaction processing features of the transactional processing platform.

### Claim 18

A method of deploying an application in a platform independent programming language 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 wherein the domain manager coordinates the deployment and distribution of transactional applications to the computing domain, the domain manager;
providing a virtual machine integration layer integrating at least one Virtual Machine (VM) with a transaction processing platform that is transparent to the platform independent language;
providing, by the domain manager node, to each of the computing nodes, a first portion of the application, wherein the first portion defines, for each computing node, a portion of the behavior of the application to be accomplished by that computing node;
receiving by each computing node at least one executable file appropriate for the portion of the behavior of the application defined, by the first portion, to be accomplished by that computing node; and
providing transaction bindings and a virtual machine interpreter to support the user-defined business logic being executed by the one or more virtual machines employing the transaction processing features of the underlying transaction processing platform;
wherein distributed applications for transaction processing on one or more virtual machines are transparently distributed and managed across multiple ones of the computing nodes.

### Claim 19 (depends on 18)

The method of claim 18, 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 application, to distribute the transactions on objects of the application across multiple ones of the computing nodes.

### Claim 20 (depends on 18)

The method system of claim 18, 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.

### Claim 21 (depends on 20)

The method of claim 20, wherein:
distributing the objects across multiple ones of the computing nodes includes replicating each of at least some of the objects from an active computing node for that object to at least one replica node for that object.

### Claim 22 (depends on 21)

The method of claim 21, wherein:
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 active, in order to continue to accomplish the behavior of the application in a fault tolerant manner, without the inoperable computing node.

### Claim 23 (depends on 18)

The method of claim 18, further comprising:
executing a deployment tool to define which computing nodes form the computing domain.

### Claim 24 (depends on 18)

The method of claim 18, further comprising:
configuring the deployment 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 application; and
wherein data required by a portion of the behavior of the application defined, by the first 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.

### Claim 25 (depends on 18)

The method of claim 18, wherein a new node joins a domain that is currently executing an application, the application is deployed to the new node transparently.

### Claim 26 (depends on 18)

The method of claim 18, wherein code of the platform independent programming language of the application transparently executes with transaction processing semantics.

### Claim 27 (depends on 18)

The method of claim 18, wherein a user-defined business logic specified in the platform independent language is executed on a Virtual Machine and transparently accesses transaction processing features of the transactional processing platform.

### Claim 28 (depends on 18)

The method of claim 18, wherein a user-defined business logic specified in the platform independent language is executed on a Virtual Machine and transparently accesses transaction processing features of the transactional processing platform.

### Claim 29

A computing system configured to deploy an application in a platform independent programming language for execution in a distributed manner, comprising:
a plurality of computing nodes;
a virtual machine integration layer integrating at least one Virtual Machine (VM) with a transaction processing platform that is transparent to the platform independent language; and
the plurality of computing nodes configured to execute computer program instructions to accomplish a fully transactional application, including managed objects, where the managed objects are persisted in a shared memory of the computing system, such that a scope of the objects is global to the transactional application and operations on the managed objects are restricted to being carried out with respect to a transaction being processed by the fully transactional application;
wherein the integration layer includes at least one of service adaptors and transaction bindings to support user-defined business logic being executed by the one or more virtual machines employing the transaction processing features of the underlying transaction processing platform.

### Claim 30 (depends on 29)

The computing system of claim 29, wherein:
the managed objects are configured to be transactionally mirrored from a first node of the plurality of nodes to a backup node of the plurality of nodes.

### Claim 31 (depends on 29)

The computing system of claim 29, wherein:
the managed objects have associated timers via which transaction deadlocks are detectable.

### Claim 32 (depends on 29)

The computing system of claim 29, wherein:
the system is further configured to, for an object being read and then set, promote a read lock operable during the read operation to a write lock operable during the write operation.

### Claim 33 (depends on 29)

The computing system of claim 29, wherein:
the system is further configured to, for an object being read, to generate a write lock on that object without generating a read lock on that object.

### Claim 34

A computing system, comprising:
at least one computing device configured to execute computer program instructions to accomplish a fully transactional application, including managed objects, wherein:
the managed objects are persisted in a shared memory of the computing system, such that a scope of the objects is global to the transactional application; and
operations on the managed objects are restricted to being carried out with respect to a transaction being processed by the fully transactional application.

### Claim 35 (depends on 34)

The computing system of claim 34, wherein:
the managed objects are JAVA objects configured to be distributed such that the managed JAVA objects are accessible from at least one JAVA Virtual Machine (JVM).

### Claim 36 (depends on 35)

The computing system of claim 35, wherein:
the managed distributed JAVA objects are configured to be accessible across all the instances of the JVM.

### Claim 37 (depends on 35)

The computing system of claim 35, wherein:
the managed Java objects are configured to be executed by a plurality of nodes of a domain; and the managed Java objects are configured to be transactionally mirrored from a first node of the plurality of nodes to a backup node of the plurality of nodes.

### Claim 38 (depends on 37)

The computing system of claim 37, wherein:
the managed Java objects have associated timers via which transaction deadlocks are detectable.

### Claim 39 (depends on 38)

The computing system of claim 38, wherein:
the system is further configured to, for detected transaction deadlocks, roll back the detected deadlocked transactions.

### Claim 40 (depends on 39)

The computing system of claim 39, wherein:
rolling back a detected deadlocked transaction includes returning objects, that were modified by the detected deadlocked transactions, to a state of those objects just prior to the detected deadlocked transaction.

### Claim 41 (depends on 34)

The computing system of claim 34, wherein:
the system is further configured to, for an object being read and then set, promote a read lock operable during the read operation to a write lock operable during the write operation.

### Claim 42 (depends on 34)

The computing system of claim 34, wherein:
the system is further configured to, for an object being read, to generate a write lock on that object without generating a read lock on that object.

### Claim 43 (depends on 37)

The computing system of claim 37, wherein:
the system is further configured to manage a Java object of a distributed transactional application across multiple nodes by coordinating the operation of the nodes such that the Java object is consistently treated on the multiple nodes.

### Claim 44 (depends on 42)

The computing system of claim 42, wherein:
the Java object being consistently treated on the multiple nodes includes treating the object, across nodes, in a transactional manner.

### Claim 45 (depends on 34)

The computing system of claim 34, wherein:
the system is configured such that when multiple transactions attempt to promote a read lock on the same object, all of the multiple transactions but one will generate a promotion deadlock for that object; and
the promotion deadlock causes the transaction to rollback, dropping read locks on that object.

### Claim 46 (depends on 45)

The computing system of claim 45, wherein:
the system is further configured to replay each rolled back transaction, causing the rolled back transactions to reacquire the locks on that object.
