Tracking down an unknown port on server startup [fixed]

I have recently downloaded wos2wsas 3.2.0 and am running via bin/wso2server.bat on Windows. As the system initializes, a port (26000+) is opened for listening that I can't identify. With each successive stop and restart, the port being opened increments by an amount that appears to be based upon the startup time (by ~8 per minute?)   Here are steps to reproduce/see what I'm talking about in more detail... Open 2 command prompts. First shell: navigate to where wso2wsas is extracted/installed, into the bin folder, and start the app via wso2server.bat Second: Issue netstat -a -n -o -p TCP | find "LISTENING" In the results of the second window, locate the PID that started the port(s) expected for http and/or https transports Look at other ports being listened by the same process, and you should see one that is a high port number. Also appears that it is not bound to any specific address, so its open to everyone to connect to.   I can't find documentation on this port, why its opened or how. The port shuts down when the server exits. If you telnet connect to the port, you can establish connection and type up to 5 characters (6 will drop the connection). Is this some kind of command port?  Is it related to embedded tomcat?   This is also the same question posted by jon at http://wso2.org/forum/thread/10277 Solution: disable/remove references to -Dcom.sun.management.jmxremote within bin/wso2server.bat repository/conf/wrapper.conf