Vladimir Matena

6807547, Oct 19, 2004

May 3, 2001

09/848802

Vladimir Matena - Redwood City CA
Mark W. Hapner - San Jose CA

Sun Microsystems, Inc. - Santa Clara CA

G06F 700

707103R, 707 10

Methods and apparatus for implementing state machines as enterprise beans with reliable or transactional timers on an enterprise platform are disclosed. According to one aspect of the present invention, a state machine is arranged to be used within a computing system that supports an enterprise platform. The state machine includes an entity object, a home interface associated with the entity object, and a remote interface associated with the entity object. The home interface is arranged to create, find, and remove entity objects, while the remote interface is arranged to drive the state machine. The entity object is arranged to be deployed in a bean container, which includes a timer. In addition to including a timer, the bean container is arranged to invoke the entity object using the remote. In one embodiment, the timer is transactional.

6832238, Dec 14, 2004

May 24, 2000

09/578266

Rahul Sharma - Sunnyvale CA
Vladimir Matena - Redwood City CA

Sun Microsystems, Inc. - Santa Clara CA

G06F 1516

709201, 709202, 712 28, 707 3

The present invention defines a transaction management contract between an application server and a resource adapter and its underlying resource manager that allows an application server to utilize local transactions on a resource manager and avoid the overhead of an external transaction manager. The transaction management contract incorporates two aspects that apply to different types of transactions. The first aspect provides an application level transaction contract between a transaction manager and a resource manager based on javax. transaction. xa. XAResource of the J2EE specification. The second aspect is local transaction management contract. These contracts enable application server to provide the infrastructure and runtime environment for transaction management. An application component relies on this transaction infrastructure to support its component level transaction model.

6877111, Apr 5, 2005

Mar 26, 2001

09/818214

Rahul Sharma - San Jose CA, US
Vladimir Matena - Redwood City CA, US
Masood Mortazavi - Cupertino CA, US
Sanjeev Krishnan - Cupertino CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F011/00

714 13, 714 6, 714 15

An invention is disclosed managing the replicated and migration capable state for an enterprise Java bean (EJB) application. The invention includes executing a Java application on a server that includes an entity bean. In addition, a replicated state manager is executed that includes program instructions for managing an in-memory state of the Java application, and program instructions for replicating the in-memory state of the Java application to a replicated state server. The replicated state server can be a memory replicated state server, or a disk replicated state server. To facilitate application state management, embodiments of the present invention store states of the entity beans objects using state objects, which are updated in response to changes in the state of the application. Hence, the embodiments of the present invention define a logical separation between the application and the state objects.

6892382, May 10, 2005

May 3, 2000

09/564067

Mark W. Hapner - San Jose CA, US
Vladimir Matena - Redwood City CA, US
Kevin Osborn - Newton MA, US
Hans Hrasna - Carlisle MA, US

Sun Microsystems, Inc. - Palo Alto CA

G06F009/44
G06F009/445

717174, 717168

Methods and apparatus for implementing deployment descriptors which are used to deploy modules in an enterprise environment are disclosed. According to one aspect of the present invention, a method for deploying an application using a deployment tool for use on a platform server includes creating the application, creating an application deployment descriptor for the application, packaging the application in an archive, and deploying the application packaged in the archive. Creating the application includes obtaining an application component which has an associated application component deployment descriptor that has information relating to the deployment of the application component. The application deployment descriptor for the application includes information arranged to identify the application component, and packaging the application in an archive includes packaging the application component, the application component deployment descriptor, and the application deployment descriptor. The application packaged in the archive is deployed using the application component deployment descriptor.

6912569, Jun 28, 2005

Apr 30, 2001

09/846492

Rahul Sharma - San Jose CA, US
Vladimir Matena - Redwood City CA, US
Masood Mortazavi - Cupertino CA, US
Sanjeev Krishnan - Cupertino CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F015/173
G06F003/00

709223, 709224, 719315, 719316

An invention for migrating managed application state for a Java based application is disclosed. A first Java module is executed on a first server. The first Java module includes a first entity bean and a first state object in communication with the first entity bean. The first state object stores a state of the first entity bean. The first state object is replicated to a state server or stored in-memory and made capable of migration by replicated state manager. Then, a second Java module is started on a second server as part of the module migration by a control module. The second Java module includes a second state object that is populated with state by either recovering from replica of fist state object stored on the state server or by getting transferred state of an in-memory copy of first state object managed on first server.

6922796, Jul 26, 2005

Apr 11, 2001

09/833856

Vladimir Matena - Redwood City CA, US
Rahul Sharma - San Jose CA, US
Masood Mortazavi - Cupertino CA, US
Sanjeev Krishnan - Cupertino CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F011/00
G01R031/28

714 48, 717124

An invention is disclosed for performing failure recovery in a Java platform. An application is executed that includes a service module and a control module. The control module includes application-specific polices for the application. When an error is detected in a system component, the detected error is reported to a runtime executive, and the system component is isolated. The control module is then notified of the system component failure.

7165108, Jan 16, 2007

Mar 19, 2001

09/812537

Vladimir Matena - Redwood City CA, US
Rahul Sharma - Sunnyvale CA, US
Masood Mortazavi - Cupertino CA, US
Sanjeev Krishnan - Cupertino CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F 15/173
G06F 9/46
G06F 3/00

709226, 719317, 718105

An invention is disclosed for a load balancing method in a JAVA based environment. The method includes executing an application having a first service module and a control module. The control module includes application-specific policies for the application. During execution, the utilization of system resources is sensed. In response to the sensed utilization of system resources, a second service module is generated using the first service module. In addition, the state of the first service module is transferred to the second service module, and the first service module is terminated. To sense the system resource utilization, embodiments of the present invention can poll system resources, or receive notifications from the system resources. Further, some embodiments of the present invention include application-specific policies that include specific servers on which to generate the second service module during load balancing or module moving.

7168088, Jan 23, 2007

Nov 20, 2000

09/849605

Vladimir Matena - Redwood City CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F 17/00
G06F 17/30
G06F 15/16

726 3, 726 1, 726 2, 709217, 709218, 709219

A method and apparatus for fast and reliable fencing of resources such as shared disks on a networked system. For each new configuration of nodes and resources on the system, a membership program module generates a new membership list and, based upon that, a new epoch number uniquely identifying the membership correlated with the time that it exists. A control key based upon the epoch number is generated, and is stored at each resource controller and node on the system. If a node is identified as failed, it is removed from the membership list, and a new epoch number and control key are generated. When a node sends an access request to a resource, the resource controller compares its locally stored control key with the control key stored at the node (which is transmitted with the access request). The access request is executed only if the two keys match. The membership list is revised based upon a node's determination (by some pre-determined criterion or criteria, such as slow response time) of the failure of a resource, and is carried out independently of any action (either hardware or software) of the failed resource.