| Author |
Java RMI
|
Christopher Keah
Greenhorn
Joined: Apr 21, 2012
Posts: 2
|
|
I got an issue running the java RMI tutorial on my macbook.
I can start the RMI registry the first time I run the server app.
But the 2nd and subsequent run, I get the following exception.
I do the following,
It looks like the RMI registry is already running in the background or the port is never freed after the server application terminates.
Any ideas?
|
 |
Pat Farrell
Rancher
Joined: Aug 11, 2007
Posts: 4422
|
|
This answer doesn't help with your specific issue, but why are you trying to use RMI?
Its completely obsolete. See http://www.coderanch.com/t/570237/java/java/Why-there-still-interest-lots
|
 |
Christopher Keah
Greenhorn
Joined: Apr 21, 2012
Posts: 2
|
|
Thanks.
I do understand that RMI is "blown glass" fragile.
I'm trying to get familiar with the protocol for an upcoming SCJD.
|
 |
Pat Farrell
Rancher
Joined: Aug 11, 2007
Posts: 4422
|
|
Christopher Keah wrote:I'm trying to get familiar with the protocol for an upcoming SCJD.
Best of luck on the test.
I do wish they would drop that whole topic. Would be better for all of us.
|
 |
yadave Franklin
Greenhorn
Joined: Apr 30, 2012
Posts: 1
|
|
This tutorial attempts to appearance the aspect of RMI, after discussing any accidental features. Sun has provided a Adviser to RMI, but it includes a lot of actual that is not accordant to RMI itself. For example, it discusses how to absorb RMI into an Applet, how to use bales and how to abode aggregate classes in a altered agenda than the antecedent code. All of these are absorbing in themselves, but they accept annihilation at all to do with RMI. As a result, Sun's adviser is unnecessarily confusing. Moreover, Sun's adviser and examples omit a amount of data that are important for RMI.
There are three processes that participate in acknowledging limited adjustment invocation.
|
 |
 |
|
|
subject: Java RMI
|
|
|