RMI registry blocked at port 1099

[sagar_sawant]

I tried to start up my RMI registry on a Windows 2000 server, which by
default starts at port 1099. I got an error stating that port 1099 was
already in use. I confirmed that port 1099 was in fact in use, by using
netstat. I then used fport to find out which process was using port
1099. It turns out that the process using port 1099 was "System" with a
pid of 8. I looked at a couple of other Windows machines and it looks
like "System" is always running and listens on various ports such as
ports 139, 427, 445, etc. Bouncing the server fixed the problem. When
the server came up, "System" was no longer listening on port 1099, but
it was still listening on other ports. Does anyone know what "System"
is and why it could have been listening on port 1099.

Thanks,
Sagar

 

[Ross Bamford]

I tried to start up my RMI registry on a Windows 2000 server, which by
default starts at port 1099. I got an error stating that port 1099 was
already in use. I confirmed that port 1099 was in fact in use, by using
netstat. I then used fport to find out which process was using port
1099. It turns out that the process using port 1099 was "System" with a
pid of 8. I looked at a couple of other Windows machines and it looks
like "System" is always running and listens on various ports such as
ports 139, 427, 445, etc. Bouncing the server fixed the problem. When
the server came up, "System" was no longer listening on port 1099, but
it was still listening on other ports. Does anyone know what "System"
is and why it could have been listening on port 1099.

Thanks,
Sagar

Whatever it is, I'll bet it's not written in Java... Don't they have a
comp.os?

(It's probably the RegisterUserDetailsAndSellThemToTheTelemarketers
daemon from sex-trojans.com...)

 

[.]

I tried to start up my RMI registry on a Windows 2000 server, which by
default starts at port 1099. I got an error stating that port 1099 was
already in use. I confirmed that port 1099 was in fact in use, by using
netstat. I then used fport to find out which process was using port
1099. It turns out that the process using port 1099 was "System" with a
pid of 8. I looked at a couple of other Windows machines and it looks
like "System" is always running and listens on various ports such as
ports 139, 427, 445, etc. Bouncing the server fixed the problem. When
the server came up, "System" was no longer listening on port 1099, but
it was still listening on other ports. Does anyone know what "System"
is and why it could have been listening on port 1099.

This is really a question about Windows and not about Java. "System" is a
local user with certain privledges on your computer. Things like the video
driver, hard drive controller, etc. must be started before you can log in.
All these things are run as Services. When you create a Service it must
run as a particular user. All Windows machines have a Local user called
"System" that is typically used to run these Services.

This is all similar to daemons on UNIX. If you want to know more about
Services and the user "System" you should check with a Windows group or
google for "Windows Administration".

 

[dpenney]

So use a different port

 

[Esmond Pitt]

So use a different port

So tell Microsoft to get the hell out of using port 1099 which is
allocated by IANA to the RMI Registry and has been for at least eight years.

 

[dpenney]

Chances are it was the RMI Registry that was running in the first place
and nothing to do with Microsoft which is why rebooting fixed things.
Pretty easy to hang ports when experimenting with java code.