Results 11 to 12 of 12
Are you sure your java app is not forking processes? That would explain the many open ports....
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 05-11-2012 #11
The adventure of a life time.
Linux User #296285
- 06-25-2012 #12
- Join Date
- May 2012
Thanks for your help. Finally I found the root cause of this issue. We used JMX agent for monitoring Java application. The JMX agent is the root cause for the random LISTEN port. You can find more details in the below link,
link : stackoverflow.com/questions/516142/does-java-6-open-a-default-port-for-jmx-remote-connections
More details about remote monitoring and agent please refer below link,
link : docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html
Remote Monitoring and Management To enable monitoring and management from remote systems, you must set the following system property when you start the Java VM. com.sun.management.jmxremote.port=portNum In the property above, portNum is the port number through which you want to enable JMX RMI connections. Be sure to specify an unused port number. In addition to publishing an RMI connector for local access, setting this property publishes an additional RMI connector in a private read-only registry at the specified port using a well known name, "jmxrmi".