Re: Decrease time out period if server is not registered in the rmiregistery

On Wed, 21 Mar 2007 15:24:59 +0800, ashwin.dasanahalli@xxxxxxxxx wrote
(in article <1174461899.457001.224860@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>):

I have written a tiny RMI client. Before I bind to the RMI server, I'm
doing a Naming.lookup to check if the server is registered. It is
taking too much time to throw an exception if the server is not
registered in the rmiregistery. Is there any way I can decrease this
time???

Any help will be appreciated..........

Thanks
Ashwin

we did an analysis of this problem about a year ago, in the java group. it
is a problem with various windows platforms and the implementation of the
look-up, if the ip port does not respond.

Even setting a time-out value on a port you open will not circumvent the
problem.

as i say It was worse on windows, and non-existent on OSX, but recently even
that platform is ignoring the time out values, so that if it is set for 5
seconds , it can still take like 30!!!

AHHHH you lucky guy, I still have the notes from another java group.
here we found 4 seconds on an internal network.


/* bug found on windows!!
Output for this always is something like
< ----------------------------------------------------------------
4802
282
281
282
266
282
281
282
281
282
282
4771
problem found: the JVM is running on Windows XP with netbios over
TCP/IP activated. On connect() the JVM tries to resolve the hostname
(java.net.InetAddress.getHostFromNameService, getHostByAddr).

Windows tries a netbios ns query on udp port 137 with a timeout of
1500ms, ignores any ICMP "port unreachable" packages and repeats this
two more times, adding up to a value of 4.5 seconds (!).

Deactivating netbios "fixes" this, but isnŽt always an option ... any
ideas very welcome.

*/




Steve








Steve






.

Relevant Pages

  • Re: How to Maintain an IIS Server?
    ... > server running on a Windows 2000 server. ... before a firewall and antivirus have been installed]. ... open ports; however, this will not identify which program is using the port. ...
    (microsoft.public.inetserver.iis.security)
  • LPD/LPR printing or alternative
    ... Configuring LPD for Microsoft Windows XP or Windows 2003 Server ... LPR port. ... protocol address of the HP Jetdirect print server. ...
    (comp.os.os2.misc)
  • RE: xp pro sharing printer
    ... How to troubleshoot network printing problems in Windows XP ... SMB-connected print server ... Incompatible print driver ... and then redirect the port to the network server. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: How to Maintain an IIS Server?
    ... >> server running on a Windows 2000 server. ... > before a firewall and antivirus have been installed]. ... > program or executable using that port. ...
    (microsoft.public.inetserver.iis.security)
  • RE: Printing from Win9x clients stops
    ... since this issue only occurs on all Windows 9x ... Open Server Management Console, ... Verify basic network connectivity. ... >> Create a local printer and in the Ports section, ...
    (microsoft.public.windows.server.sbs)