解决后的一个小结：
此处是一个tomcat端口，这种情况下，可以先在浏览器访问下看看效果，就可以快速定位
又发现一个简单的办法：
下面的定位过程，适用于各种场合
无意中发现有个进程开了好多端口，很奇怪
看看这个java.exe的启动参数：jinfo
64位环境：jinfo -J-d64 pid
The jinfo command prints Java configuration information for a specified Java process or core file or a remote debug server.
The configuration information includes Java system properties and Java Virtual Machine (JVM) command-line flags.
If the specified process is running on a 64-bit JVM, then you might need to specify the -J-d64 option,
for example: jinfo -J-d64 -sysprops pid.
This utility is unsupported and might not be available in future releases of the JDK.
In Windows Systems where dbgeng.dll is not present, Debugging Tools For Windows must be installed to have these tools working.
The PATH environment variable should contain the location of the jvm.dll
that is used by the target process or the location from which the crash dump file was produced.
For example, set PATH=%JDK_HOME%\jre\bin\client;%PATH% .
http://docs.oracle.com/javase/8/docs/technotes/tools/unix/jinfo.html
有一个奇怪的地方jps、jconsole.exe和jvisualvm.exe中都看不到4036的进程
最后通过procexp64.exe来查看
原来是Jenkins，有浏览器访问下看看：