Duplicated naming service in a distributed processing system

• US 7,480,679 B2
• Filed: 04/11/2005
• Issued: 01/20/2009
• 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: Jacobs, Dean B., Halpern, Eric M.
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US11/103,054
• Publication Number:
  US 20050203986A1
• Time in Patent Office: 1,380 Days
• Field of Search: 707/10, 707/200, 707/201, 709/228, 709/238, 709/221, 709/219, 712/27
• US Class Current: 1/1
• 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
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A clustered enterprise Java™ distributed processing system is provided. The distributed processing system includes a first and a second computer coupled to a communication medium. The first computer includes a Java™ virtual machine (JVM) and kernel software layer for transferring messages, including a remote Java™ 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. The computers may be programmed in a stateless, stateless factory, or a stateful programming model. The clustered enterprise Java™ distributed processing system allows for enhanced scalability and fault tolerance.

Claims

1. A method for providing a replicated naming service in a network for use in accessing service providers located at a plurality of processing devices, comprising the steps of:

maintaining service provider information within the network by providing a first naming service at a first processing device, and a second naming service at a second processing device, wherein both the first and second naming services have service pools that include replica aware stubs for each service provider providing a similar service;

receiving at the first naming service a message from the second processing device that indicates a change in at least one instance of a service provider at the second processing device; and

modifying the first naming service according to the message to reflect the change in the instances of service providers at the second processing device.

2. A method according to claim 1, wherein the step of modifying the first naming service further comprises:

classifying the instance of the service indicated by the message according to a service type; and

modifying a portion of the first naming service corresponding to the service type according to the message, wherein the portion of the first naming service includes a plurality of instances of a service of the service type.

3. The method of claim 2, wherein the step of modifying a portion of the first naming service further comprises the steps of:

creating a reference to the instance of the service indicated by the message, wherein the reference enables access to the instance of the service by a service user; and

adding the reference to the portion of the first naming service corresponding to the service type.

4. The method of claim 3, wherein the service user is any of an object, application, or Java Bean.

5. The method of claim 1, further comprising the step of:

receiving at either of the processing devices a request from a client to lookup a service provider from either one of said naming service trees, and communicating the location of the service provider to the client.

6. The method of claim 5 wherein the lookup by the client enables the client to obtain a replica aware stub from the naming service tree on that processing device.

7. The method of claim 6 wherein the replica aware stub contacts the service pool to refresh the client'"'"'s list of available service providers.

8. A system for providing a replicated naming service in a network for use in accessing service providers located at a plurality of processing devices, comprising:

a communication medium;

a first processing device having a first naming service, and a second processing device having a second naming service, wherein both the first and second naming services have service pools that include replica aware stubs for each service provider providing a similar service;

software code for receiving at the first naming service a message from the second processing device that indicates a change in at least one instance of a service provider at the second processing device; and

software code for modifying the first naming service according to the message to reflect the change in the instances of service providers at the second processing device.

9. The system according to claim 8, wherein the software code for modifying the first naming service further comprises:

software code for classifying the instance of the service indicated by the message according to a service type; and

software code for modifying a portion of the first naming service corresponding to the service type according to the message, wherein the portion of the first naming service includes a plurality of instances of a service of the service type.

10. The system of claim 9, wherein the software code for modifying a portion of the first naming service further comprises code for:

creating a reference to the instance of the service indicated by the message, wherein the reference enables access to the instance of the service by a service user; and

adding the reference to the portion of the first naming service corresponding to the service type.

11. The system of claim 10, wherein the service user is any of an object, application, or Java Bean.

12. The system of claim 8, further comprising software code for receiving at either of the processing devices a request from a client to lookup a service provider from either one of said naming service trees, and communicating the location of the service provider to the client.

13. The system of claim 12 wherein the lookup by the client enables the client to obtain a replica aware stub from the naming service tree on that processing device.

14. The system of claim 13 wherein the replica aware stub contacts the service pool to refresh the client'"'"'s list of available service providers.

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

maintaining service provider information within a network by providing a first naming service at a first processing device, and a second naming service at a second processing device, wherein both the first and second naming services have service pools that include replica aware stubs for each service provider providing a similar service;

receiving at the first naming service a message from the second processing device that indicates a change in at least one instance of a service provider at the second processing device; and

modifying the first naming service according to the message to reflect the change in the instances of service providers at the second processing device.

16. A method according to claim 15, wherein the step of modifying the first naming service further comprises:

classifying the instance of the service indicated by the message according to a service type; and

modifying a portion of the first naming service corresponding to the service type according to the message, wherein the portion of the first naming service includes a plurality of instances of a service of the service type.

17. The computer readable medium of claim 16, wherein the step of modifying a portion of the first naming service further comprises the steps of:

creating a reference to the instance of the service indicated by the message, wherein the reference enables access to the instance of the service by a service user; and

adding the reference to the portion of the first naming service corresponding to the service type.

18. The computer readable medium of claim 17, wherein the service user is any of an object, application, or Java Bean.

19. The computer readable medium of claim 15, further comprising instructions for:

receiving at either of the processing devices a request from a client to lookup a service provider from either one of said naming service trees, and communicating the location of the service provider to the client.

20. The computer readable medium of claim 19 wherein the lookup by the client enables the client to obtain a replica aware stub from the naming service tree on that processing device.

21. The computer readable medium of claim 20 wherein the replica aware stub contacts the service pool to refresh the client'"'"'s list of available service providers.