I had this stupid problem when copying a JBoss configuration from one machine to another, that the TCP/IP ports which are needed appear to be in use.
My original idea was that a running instance of JBoss ( or even, though I doubted that) another program would be hanging around.
Running the command (as this was on a linux machine)
allowed me to rule out that option. So it had to be something else.
After some more thinking, it dawned on me. Since JBoss 4.2, the default option is to bind all network stuff to the loopback address (127.0.0.1, usually referred to as “localhost”) only. So I had updated the startup script to include ‘–host “192.168.0.206”‘. Changing that to ‘–host “0.0.0.0”‘ did the trick and fixed the problem.