Browse Prior Art Database

ENHANCED AND PERSISTENT REPLACEMENT FOR RMI REGISTRY

IP.com Disclosure Number: IPCOM000015810D
Original Publication Date: 2002-Nov-29
Included in the Prior Art Database: 2003-Jun-21
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

Invention Non-local and persistent RMI registry Problem RMI (Remote Method Invocation) is a Java* protocol for accessing remote objects. Distributed objects use the RMI registry to register themselves, and to locate other distributed objects in the system. The main operations provided by the registry are Bind and Locate. One problem is that the RMI registry is volatile, which causes any client-server application to have a single point of failure: If the server containing the RMI registry fails, distributed objects become unable to register themselves (bind) and to find (locate) each other. Another problem is that the RMI registry must be local to the host computer for binding, which introduces a limitation for real distributed systems, with remote objects residing throughout the numerous servers: where would you place your RMI registry?

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 57% of the total text.

Page 1 of 1

ENHANCED AND PERSISTENT REPLACEMENT FOR RMI REGISTRY

Invention

    Non-local and persistent RMI registry Problem

    RMI (Remote Method Invocation) is a Java* protocol for accessing remote objects. Distributed objects use the RMI registry to register themselves, and to locate other distributed objects in the system. The main operations provided by the registry are Bind and Locate.

    One problem is that the RMI registry is volatile, which causes any client-server application to have a single point of failure: If the server containing the RMI registry fails, distributed objects become unable to register themselves (bind) and to find (locate) each other. Another problem is that the RMI registry must be local to the host computer for binding, which introduces a limitation for real distributed systems, with remote objects residing throughout the numerous servers: where would you place your RMI registry?

Solution

    The proposed solution provides a way to solve both problems. It lifts the requirement for the RMI registry to be local to the host computer, and makes the RMI registry persistent. The solution uses a relational database to store the registry information. This database replaces the RMI registry. Using this solution makes RMI more robust, and supports RMI protocol for truly distributed systems.

    The proposed abstraction replaces the RMI registry with an independent data structure stored in a relational database that can be accessed on via simple queries
(i.e., SQL statemen...