Smart stub or enterprise java bean in a distributed processing system
First Claim
1. An article of manufacture including a non-transitory 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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
32 Claims
-
1. An article of manufacture including a non-transitory 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
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. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
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. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24)
-
-
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. - View Dependent Claims (26, 27, 28, 29, 30, 31, 32)
-
Specification