-
1. Re: How to bind to all interfaces on JBoss 5.1
peterj Sep 10, 2009 2:29 PM (in response to ngtdave)Is this a typo: -b0.0.0.0
It should be: -b 0.0.0.0
How did you change the run.bat? According to the error message you appear to have set the bind address to "/0.0.0.0" and not "0.0.0.0". -
2. Re: How to bind to all interfaces on JBoss 5.1
peterj Sep 10, 2009 2:30 PM (in response to ngtdave)Also, I recommend that instead of changing run.bat you create a new batch file that contains:
call run.bat -b 0.0.0.0 -
3. Re: How to bind to all interfaces on JBoss 5.1
ngtdave Sep 10, 2009 3:50 PM (in response to ngtdave)Thank you for your quick reply PeterJ!
You are right, I meant -b 0.0.0.0 but the log definitely says "/0.0.0.0", I'm not sure why.
Anyway, just tried again and it seems a good old fashion Windows reboot fixed the problem. I should have known, I've seen this with other ports Windows randomly takes. I would add this port to the list of reserved ports in Windows (so it won't take it) but I'm not sure what "port 4,712" means... I assume 4712.
Anyway, thank you again for your help, I hope this helps others as well. -
4. Re: How to bind to all interfaces on JBoss 5.1
peterj Sep 10, 2009 4:19 PM (in response to ngtdave)You can use netstat, or better yet, TCPView from sysinternal, to see what apps are using a port (4712 in this case). Some Windows apps, notably the MS Sync Center and virus scanners, seem to take random ports that JBoss AS later wants.