we have the same problem.
one (dirty) solution is to install jboss as a service (with f.e. javaservicent). when the machine is starting up, the jboss- service will be startet before the other (windows-)-service blocking port 1099 and then it works fine.
we do not even have problems after that when stopping jboss and restart it.
we are still doing research to track down the service/function blocking port 1099.
In the netstat you can see the PID that use the port.
Go to task manager and look which program is runnig under the PID.
this is NT only (I think),
I do not found it on XP,
I do not find how to restrict dynamic ports (1024-...) on XP.
Maybe some M$ experts can help ???
> In the netstat you can see the PID that use the
> Go to task manager and look which program is runnig
> under the PID.
Really? How? It'd be most useful, but ....
-o Displays the owning process ID associated with each connection.
my netstat doesn't seem to support that option (win2k adv server ...)
I had this problem today and thought I'd share my findings in case it helps anyone.
There are a few service on W2K server that get a dynamically allocated port. If JBoss isn't already running then these will get allocated. I have had it most frequently with 1099 and 1098. This tool is an easy way of finding which process has taken the port JBoss needs:
For me this has mostly been the File Replication Service or IIS Admin Service Helper. You can just stop those ervices whilst you startup JBoss and re-start them subsequently.