Re: ServerRef with persistent ObjID

Robert DiFalco <[email protected]> Thu, 16 Feb 2006 08:39:04 -0800
Newsgroups gmane.comp.java.sun.rmi,gmane.spam.detected
Message-ID <[email protected]>
Thanks Bob. Has anyone here tried the SunJrmpExporter with any JVM
implementations other than Sun? For example, IBM?

On the JERI front, we did perform a test replacing JRMP with JERI and
one problem we came across is that JERI seemed to use twice as many
threads for RMI calls. While we hoped that the dedicated in/out threads
would be mitigated by fewer DGC threads, we still saw our application
create many more threads with JERI than with JRMP. There is probably
some JERI tuning we are not aware of that would have helped this but
threads are pretty precious to our application as we connect to many
agents. This doesn't mean that we wont switch to JERI but rather that we
need to wait until we can give it more of the attention it deserves.

R.  

-----Original Message-----
From: Bob Scheifler [mailto:[email protected]] 
Sent: Wednesday, February 15, 2006 12:00 PM
To: Robert DiFalco
Cc: [email protected]
Subject: Re: ServerRef with persistent ObjID

> I need to figure out how
> to create one of my services (essentially my server-service) with an 
> ObjID that is consistent over restarts of the JVM.

There is no standard way to do this for JRMP.  (It can easily be done
with JERI.)  For a non-standard JRMP way, you can look at the
com.sun.jini.phoenix.SunJrmpExporter class in the latest Jini Technology
Starter Kit (http://starterkit.jini.org).

- Bob

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html