-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
None
-
None
-
None
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Problem
Setting up the jConsole monitor, as described in this documentation, after set this parameter at the setenv file:
-Dcom.sun.management.jmxremote.port=9595 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx
jConsole works as expected, but during Confluence shutdown, even after close jConsole applicaion, this error is shown:
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9595; nested exception is: java.net.BindException: Address already in use
Fix
There is none yet.
Workaround
Manually kill the process at jConsole port.
- relates to
-
CONFCLOUD-22182 Address already in use when using jConsole monitor
-
- Closed
-
[CONFSERVER-22182] Address already in use when using jConsole monitor
Workflow | Original: JAC Bug Workflow v3 [ 2899957 ] | New: CONFSERVER Bug Workflow v4 [ 2994564 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2794700 ] | New: JAC Bug Workflow v3 [ 2899957 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2725000 ] | New: JAC Bug Workflow v2 [ 2794700 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2388379 ] | New: JAC Bug Workflow [ 2725000 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2264986 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2388379 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2208455 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2264986 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2190560 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2208455 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1924693 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2190560 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1731704 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1924693 ] |
Description |
Original:
h3.Problem
Setting up the jConsole monitor, as described in this [documentation|http://confluence.atlassian.com/display/DOC/Live+Monitoring+Using+the+JMX+Interface], after set this parameter at the setenv file: {code} -Dcom.sun.management.jmxremote.port=9595 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx {code} jConsole works as expected, but during Confluence shutdown, even after close jConsole applicaion, this error is shown: {code} Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9595; nested exception is: java.net.BindException: Address already in use {code} h3.Fix There is none yet. h3.Workaround Manually kill the process at jConsole port. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-22182]. {panel} h3.Problem Setting up the jConsole monitor, as described in this [documentation|http://confluence.atlassian.com/display/DOC/Live+Monitoring+Using+the+JMX+Interface], after set this parameter at the setenv file: {code} -Dcom.sun.management.jmxremote.port=9595 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx {code} jConsole works as expected, but during Confluence shutdown, even after close jConsole applicaion, this error is shown: {code} Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9595; nested exception is: java.net.BindException: Address already in use {code} h3.Fix There is none yet. h3.Workaround Manually kill the process at jConsole port. |