Clustered enterprise Java™ in a secure distributed processing system

• US 7,334,232 B2
• Filed: 07/07/2005
• Issued: 02/19/2008
• Est. Priority Date: 11/05/1998
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Langen, Anno R., Jacobs, Dean B.
• Primary Examiner(s): Nguyen; Van H.
• Application Number:
  US11/176,768
• Publication Number:
  US 20060031846A1
• Time in Patent Office: 957 Days
• Field of Search: 719/310, 719/313, 719/330, 709/201, 709/203, 709/238, 718/1
• US Class Current: 719/313
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A clustered enterprise distributed processing system. The distributed processing system includes a first and a second computer coupled to a communication medium. The first computer includes a virtual machine (JVM) and kernel software layer for transferring messages, including a remote virtual machine (RJVM). The second computer includes a JVM and a kernel software layer having a RJVM. Messages are passed from a RJVM to the JVM in one computer to the JVM and RJVM in the second computer. Messages may be forwarded through an intermediate server or rerouted after a network reconfiguration. Each computer includes a smart stub having a replica handler, including a load balancing software component and a failover software component. Each computer includes a duplicated service naming tree for storing a pool of smart stubs at a node.

Claims

1. A system for communication between processing devices in a cluster, comprising:

a first processing device, having a first virtual machine executing thereon, a first kernel layered above the first virtual machine, and a first remote method invocation layer layered above the first kernel, wherein the first kernel includes a first message data structure corresponding to a second virtual machine executing at another processing device, and wherein the first message data structure includes a first message routing software component;

a second processing device, having the second virtual machine executing thereon, a second kernel layered above the second virtual machine, and a second remote method invocation layer layered above the second kernel, wherein the second kernel includes a second message data structure corresponding to the first virtual machine executing at the first processing device, and wherein the second message data structure includes a second message routing software component; and

wherein a message is transferred from the first remote method invocation layer to the second remote method invocation layer via the first message data structure and first message routing software component on the first processing device, and the second message data structure and second message routing software component on the second processing device.

2. The system of claim 1, wherein the first remote method invocation layer comprises stubs, and the second remote method invocation layer comprises skeletons, and wherein the message is transferred from a stub in the first remote method invocation layer to a skeleton in the second remote method invocation layer via the first message data structure on the first processing device.

3. The system of claim 1, wherein the first virtual machine is a first Java virtual machine, and the first message data structure is a first remote Java virtual machine, and wherein the second virtual machine is a second Java virtual machine, and the second message data structure is a second remote Java virtual machine.

4. The system of claim 1, wherein the first message data structure further comprises a peer- gone detection software component to detect if the second virtual machine is alive.

5. The system of claim 1, further comprising:

a third processing device, having a third virtual machine executing thereon, a third remote method invocation layer, and a third kernel that includes a third message data structure corresponding to the first virtual machine executing at the first processing device;

wherein the first processing device comprises a fourth message data structure corresponding to the third virtual machine executing at the third processing device; and

wherein a message is transferred from the first remote method invocation layer to the third remote method invocation layer via the fourth message data structure on the first processing device, and the third message data structure on the third processing device.

6. The system of claim 5, wherein the first processing device and the third processing device do not have a direct socket between the devices.

7. The system of claim 6, wherein the second processing device comprises a fifth message data structure corresponding to the third virtual machine executing at the third processing device;

and

wherein during transfer of the message from the first remote method invocation layer to the third remote method invocation layer, the message is handed off from the fourth message data structure on the first processing device to the fifth message data structure on the second processing device, and thence to the third message data structure on the second processing device.

8. A method of communication between processing devices in a cluster, comprising the steps of:

providing a first processing device, having a first virtual machine executing thereon, a first kernel layered above the first virtual machine, and a first remote method invocation layer layered above the first kernel, wherein the first kernel includes a first message data structure corresponding to a second virtual machine executing at another processing device, and wherein the first message data structure includes a first message routing software component

providing a second processing device, having the second virtual machine executing thereon, a second kernel layered above the second virtual machine, and a second remote method invocation layer layered above the second kernel, wherein the second kernel includes a second message data structure corresponding to the first virtual machine executing at the first processing device, and wherein the second message data structure includes a second message routing software component; and

transferring a message from the first remote method invocation layer to the second remote method invocation layer via the first message data structure and first message routing software component on the first processing device, and the second message data structure and second message routing software component on the second processing device.

9. The method of claim 8, wherein the first remote method invocation layer comprises stubs, and the second remote method invocation layer comprises skeletons, and wherein the message is transferred from a stub in the first remote method invocation layer to a skeleton in the second remote method invocation layer via the first message data structure on the first processing device.

10. The method of claim 8, wherein the first virtual machine is a first Java virtual machine, and the first message data structure is a first remote Java virtual machine, and wherein the second virtual machine is a second Java virtual machine, and the second message data structure is a second remote Java virtual machine.

11. The method of claim 8, wherein the first message data structure further comprises a peer- gone detection software component to detect if the second virtual machine is alive.

12. The method of claim 8, further comprising:

a third processing device, having a third virtual machine executing thereon, a third remote method invocation layer, and a third kernel that includes a third message data structure corresponding to the first virtual machine executing at the first processing device;

wherein the first processing device comprises a fourth message data structure corresponding to the third virtual machine executing at the third processing device; and

wherein a message is transferred from the first remote method invocation layer to the third remote method invocation layer via the fourth message data structure on the first processing device, and the third message data structure on the third processing device.

13. The method of claim 12, wherein the first processing device and the third processing device do not have a direct socket between the devices.

14. The method of claim 13, wherein the second processing device comprises a fifth message data structure corresponding to the third virtual machine executing at the third processing device;

and

wherein during transfer of the message from the first remote method invocation layer to the third remote method invocation layer, the message is handed off from the fourth message data structure on the first processing device to the fifth message data structure on the second processing device, and thence to the third message data structure on the second processing device.

15. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:

providing a first processing device, having a first virtual machine executing thereon, a first kernel layered above the first virtual machine, and a first remote method invocation layer layered above the first kernel, wherein the first kernel includes a first message data structure corresponding to a second virtual machine executing at another processing device, and wherein the first message data structure includes a first message routing software component;

providing a second processing device, having the second virtual machine executing thereon, a second kernel layered above the second virtual machine, and a second remote method invocation layer layered above the second kernel, wherein the second kernel includes a second message data structure corresponding to the first virtual machine executing at the first processing device, and wherein the second message data structure includes a second message routing software component; and

transferring a message from the first remote method invocation layer to the second remote method invocation layer via the first message data structure and first message routing software component on the first processing device, and the second message data structure and second message routing software component on the second processing device.