SMART STUB OR ENTERPRISE JAVA BEAN IN A DISTRIBUTED PROCESSING SYSTEM

• US 20090037925A1
• Filed: 10/15/2008
• Published: 02/05/2009
• Est. Priority Date: 11/05/1998
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Halpern, Eric M., Jacobs, Dean B.
• Granted Patent: US 8,069,447 B2
• Time in Patent Office: Days
• US Class Current: 718/105
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• 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. An article of manufacture including an information storage medium wherein is stored information, comprising:

a first set of digital information at a client device, including a virtual machine with a replica-aware remote method invocation (RA RMI) stub;

wherein the RA RMI stub includes a load balancing software component and a failover software component for selecting a service provider from a plurality of service providers in a cluster;

the RA RMI stub contacts a naming service within the cluster that provides to the RA RMI stub an updated list of currently available service providers in the cluster;

the RA RMI stub uses its load balancing software component to select a service provider that provides a service requested by the client device;

the RA RMI stub invokes the requested service provided by the selected service provider using remote method invocation, wherein each of the service providers provides a remote method implementation that the RA RMI stub can communicate with using remote method invocation; and

if the selected service provider fails to respond to the remote method invocation, the RA RMI stub uses its failover software component to remove the failed service provider from the list of currently available service providers and then select a new service provider.

2. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider based on an affinity for a particular service provider.

3. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider from the plurality of service providers in a round robin manner.

4. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component randomly select a service provider.

5. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider from the plurality of service providers based upon the load of each service provider.

6. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider from the plurality of service providers based upon the data type requested.

7. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider from the plurality of service providers based upon the closest physical service provider.

8. The article of manufacture of claim 1, wherein the load balancing software component and the failover software component select a service provider from the plurality of service providers based upon a time period in which each service provider responds.

9. A method for use by a remote method invocation (RA RMI) stub stored in a processing device on a distributed processing system, which when executed by a processor performs the steps comprising:

contacting a naming service within a cluster that provides to the RA RMI stub an updated list of currently available service providers in the cluster;

selecting, by the RA RMI using its load balancing software component, a service provider from the list of currently available service providers that provides a service requested;

invoking the requested service provided by the selected service provider using remote method invocation, wherein each of the service providers provides a remote method implementation that the stub can communicate with using remote method invocation; and

if the selected service provider fails to respond to the remote method invocation, removing, by the RA RMI stub using its failover software component, the failed service provider from the list of currently available service providers and then selecting a new service provider.

10. The method of claim 9, wherein the step of selecting service provider further includes the step of:

selecting a service provider based upon an affinity.

11. The method of claim 9, wherein the step of selecting service provider further includes the step of:

selecting a service provider from the list of service providers in a round robin manner.

12. The method of claim 9, wherein the step of selecting service provider further includes the step of:

selecting a service provider randomly from the list of service providers.

13. The method of claim 9, wherein the step of selecting service provider further includes the steps of:

obtaining the load of each service provider in the list of service providers; and

selecting a service provider based upon the load of each service provider.

14. The method of claim 9, wherein the step of selecting service provider further includes the steps of:

determining the type of data requested; and

selecting a service provider from the list of service providers based upon the data type.

15. The method of claim 9, wherein the step of selecting service provider further includes the steps of:

determining the physical distance to each service provider in the list of service providers; and

selecting a service provider from the list of service providers based upon on the closest physical distance to the service provider.

16. The method of claim 9, wherein the step of selecting service provider further includes the steps of:

determining a time period for each service provider in the list of service providers to respond; and

selecting a service provider from the list of service providers based upon the time period for each service provider to respond.

17. A system for load balancing within a cluster, comprising:

a first processing device, including a virtual machine with a replica-aware remote method invocation (RA RMI) stub;

wherein the RA RMI stub includes a load balancing software component and a failover software component for selecting a service provider from a plurality of service providers in the cluster;

the RA RMI stub contacts a naming service within the cluster that provides to the RA RMI stub an updated list of currently available service providers in the cluster;

the RA RMI stub uses its load balancing software component to select a service provider that provides a service requested by the client device;

the RA RMI stub invokes the requested service provided by the selected service provider using remote method invocation, wherein each of the service providers provides a remote method implementation that the RA RMI stub can communicate with using remote method invocation; and

if the selected service provider fails to respond to the remote method invocation, the RA RMI stub uses its failover software component to remove the failed service provider from the list of currently available service providers and then select a new service provider.

18. The system of claim 17 wherein the load balancing software component and the failover software component select a service provider based on an affinity for a particular service provider.

19. The system of claim 17 wherein the load balancing software component and the failover software component select a service provider based on a round robin method.

20. The system of claim 17 wherein the load balancing software component and the failover software component randomly select a service provider.

21. The system of claim 17 wherein the load balancing software component and the failover software component select a processing device based on the load at each service provider.

22. The system of claim 17 wherein the load balancing software component and the failover software component select a service provider based on the data type requested.

23. The system of claim 17 wherein the load balancing software component and the failover software component select a service provider based on the closest physical processing device.

24. The system of claim 17 wherein the load balancing software component and the failover software component select a service provider based on time period in which each processing device responds.

25. A method of load balancing at a remote method invocation (RA RMI) stub in a cluster, comprising the steps of:

contacting a naming service within a cluster that provides to the RA RMI stub an updated list of currently available service providers in the cluster;

selecting, by the RA RMI using its load balancing software component, a service provider from the list of currently available service providers that provides a service requested;

invoking the requested service provided by the selected service provider using remote method invocation, wherein each of the service providers provides a remote method implementation that the stub can communicate with using remote method invocation; and

if the selected service provider fails to respond to the remote method invocation, removing, by the RA RMI stub using its failover software component, the failed service provider from the list of currently available service providers and then selecting a new service provider.

26. The method of claim 25 wherein said load balancing software component and the failover software component select a processing device based on an affinity for a particular service provider.

27. The method of claim 25 wherein said load balancing software component and the failover software component select a service provider based on round robin.

28. The method of claim 25 wherein said load balancing software component and the failover software component randomly select a service provider.

29. The method of claim 25 wherein said load balancing software component and the failover software component select a service provider based on the load of each service provider.

30. The method of claim 25 wherein said load balancing software component and the failover software component select a service provider based on the data type requested.

31. The method of claim 25 wherein said load balancing software component and the failover software component select a service provider based on the closest physical service provider.

32. The method of claim 25 wherein said load balancing software component and the failover software component select a service provider based on time period in which each service provider responds.