Rmi remote reference lookup very slow in web start application

Question

I have a little problem with the RMI communication in a web start test application.
It is a very simple program in which the client calls a remote object that returns a String.
Everything seems to be working fine when i'm running/debugging the client app in eclipse, but when i package my client project into a jar file and run it as a web start application (i'm providing the jnlp on a local webserver) the remote reference lookup takes about 15 seconds.
basically, what my client does is this:
Registry registry = LocateRegistry.getRegistry(address);
ServerTransaction st= (ServerTransaction) registry.lookup(name);
String result = st.test();
The server code looks like this:
String name = "ServerTransaction";
ServerTransaction engine = new DefaultServerTransaction();
ServerTransaction stub = (ServerTransaction) UnicastRemoteObject.exportObject(engine, 0);
Registry registry = LocateRegistry.createRegistry(Registry.REGISTRY_PORT);
registry.rebind(name, stub);
The server runs as a normal stand alone java application on my local machine as well.
And here the content of the jnlp file for the client application:
<resources>
     <jar href="WSTest.jar"/>
     <jar href="WSTestServer.jar"/>
     <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
     <property name="serverAddress" value="127.0.0.1" />
</resources>
<security>
     <all-permissions/>
</security>
<application-desc main-class="test.WSTest"/>
As i said, the whole thing works when run as a normal java application as well as with web start, with the difference that the remote reference lookup takes about 15 seconds with web start.
Can anyone tell me how i could go about this?

Answer 1

Meanwhile, i tried the same thing at home on my xp machine (i use vista at work), and even though my test at home basically does the same thing (invoking a simple remote method that just returns "hello world") it worked pretty fast, contary to the 15 second hang on vista.
So i can't really say where the problem is...
I also found these two rmi properties
sun.rmi.transport.connectionTimeout (1.1.6 and later)
The value of this property represents the period (in milliseconds) for which socket connections may reside in an "unused" state, before the Java RMI runtime will allow those connections to be freed (closed). The default value is 15000 milliseconds (15 seconds).
and
sun.rmi.transport.proxy.connectTimeout (1.1 and later)
The value of this property represents the maximum length of time (in milliseconds) that the Java RMI runtime will wait for a connection attempt (createSocket) to complete, before attempting to contact the server using HTTP. This property is only used when the http.proxyHost property is set and the value of java.rmi.server.disableHttp is false. The default value is 15000 milliseconds (15 seconds).
Hoping it would help (totally clueless) i tried to set these as system properties via System.setProperty(...) to a lower value (if that even works this was - please correct me if i am totally wrong here) but it didn't help.