JDK-8207048 : jhsdb debugd cannot specify a port number
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 12
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2018-07-11
  • Updated: 2020-02-11
  • Resolved: 2020-02-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8196751 - Add jhsdb option to specify debug server RMI connector port
Relates :  
JDK-8196751 - Add jhsdb option to specify debug server RMI connector port
Relates :  
JDK-8223665 - SA: debugd options should follow jhsdb style
Description
We can set a rmi registry port of debugd server by `sun.jvm.hotspot.rmi.port`, but can not set a port of RemoteObject (sun.jvm.hotspot.debugger.remote.RemoteDebuggerServer) then RemoteObject always uses an anonymous port.
Comments
Duplicate of jdk-8196751
11-02-2020
Can you include JDK-8196751 fix?
10-05-2019
I think port number should be set through command line options. If you do so, you need to wait JDK-8223665.
10-05-2019
This is an enhancement request not a bug report. It requires a CSR request to approve use of a new system property.
12-07-2018