-
Bug
-
Resolution: Fixed
-
Major
java -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar jenkins.war --deamon
results in
Forking into background to run as a daemon.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9999; nested exception is:
java.net.BindException: Address already in use
This means I cannot use VisualVM on a deamonized Jenkins instance.
I encountered this problem when using the RPM installer to setup Jenkins and afterwards manually adding the -D options to JENKINS_JAVA_OPTIONS in /etc/sysconfig/jenkins.
- is duplicated by
-
JENKINS-23023 Address already in use when starting Jenkins in daemon mode with JMX SNMP adaptor
-
- Resolved
-
- is related to
-
JENKINS-23023 Address already in use when starting Jenkins in daemon mode with JMX SNMP adaptor
-
- Resolved
-
-
JENKINS-27142 Could not listen jolokia agent port
-
- Closed
-
[JENKINS-14529] BindException when using --daemon with JMX
Summary | Original: BindException whhen using --daemon with JMX | New: BindException when using --daemon with JMX |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | New: 1.480.4-candidate |
I'm facing the same problem when trying to analyze performance issues (with jvisualvm) with our Jenkins installation.
Has there been any progress on this issue?
Does a workaround exist?