|
From: Leif M. <le...@ta...> - 2005-10-13 08:30:34
|
Arul,
Thank you for pointing this problem out. I have changed the
default ports used by
the client side of the backend socket to the range 31000-31999 and made
it possible
to set the port or port range used.
3.1.2 and earlier versions left it up to the OS to decide which port
to use.
This will be in 3.2.0.
Cheers,
Leif
arul thayalan wrote:
>Hi All,
> I'm new user to this forum. Very nice meet you
>all through this forum.
>
> My application is Java RMI based. It uses
>Wrapper service to run my applicaton as window nt
>service application. My application starts with
>binding the RMI registry with port number 1099.
>Strangely I'm facing some issues. My services are
>configured in such way that when machine restart,my
>services also restart.I will write the scenario here.
>
>1. I stopping my rmi services.
>2. I'm restarting my machine.
>3. application services starts with RMI Registry
>binding when system reboots.
>
>Here i'm facing the problem that RMI registry couldn't
>bind port number 1099 already in use.
>
>I went to cmd mode and run the command c:\>netstat -na
>It showing that 1099 holding by some local services.
>cmd result
>
>proto local address foreign address state
>--------------------------------------------
>TCP 127.0.0.1:1099 127.0.0.1:32000 ESTABLISHED
>TCP 127.0.0.1:32000 0.0.0.0 LISTENING
>
>
>My question here is
>
> Is wrapper services using port 1099 for server socket
>listening? If it using this port how can i avoid?
>Please advise me...
>
>
>Regards
>M.Arul Thayalan.
>
>
|