Nodeagent compaining about port in use - even though the port in question is free

When starting a nodeagent (I imagine any other WAS JVM would also complain in the same way) a "port in use" error is displayed and the JVM will not start. However, when you have a look with netstat -an the port is clearly not in use (OK it'll be in TIME_WAIT for a minute because your JVM did try to initialize it but if you wait a while you'll see the TIME_WAIT will dissapear) 

Simple slip-up when doing an automated build which resulted in the hostname in serverindex.xml being incorrect. Change all occurrences to the correct hostname (i.e the hostname of the nodeagent) and all will be well.


Don't forget to change it in the DMGR profile also, otherwise next time you sync you'll distribute the dodgy serverindex.xml