<div>
<div class="content wysiwyg-content">
My client uses a dial-up networking connection to my server.<br />
The client makes several RMI calls to fetch login information.<br />
<br />
Now my problem is this:<br />
<br />
If the dial-up connection hangs up for some reason during RMI calls, a new dial-up and client start do nothing. It seems like the previous RMI call is still alive (even if the applet was killed) and blocking a socket. The line is ok, no problem there, but the login does not proceed.<br />
<br />
Can the RMI connections be &quot;cleaned&quot;? Does the cleaning have to take place on the client (obviously, since it does not work) and in the server?<br />

</div>
</div>


My client uses a dial-up networking connection to my server.
The client makes several RMI calls to fetch login information.

Now my problem is this:

If the dial-up connection hangs up for some reason during RMI calls, a new dial-up and client start do nothing. It seems like the previous RMI call is still alive (even if the applet was killed) and blocking a socket. The line is ok, no problem there, but the login does not proceed.

Can the RMI connections be "cleaned"? Does the cleaning have to take place on the client (obviously, since it does not work) and in the server?


RMI method call, how to deal with line hangup?

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.