RFR: 8263565: NPE was thrown when sun.jvm.hotspot.rmi.serverNamePrefix was set
Chris Plummer
cjplummer at openjdk.java.net
Tue Mar 16 02:02:09 UTC 2021
On Tue, 16 Mar 2021 01:28:49 GMT, Yasumasa Suenaga <ysuenaga at openjdk.org> wrote:
>>> I think the default rmi registry port is 1099. However, do we need to also support something like [JDK-8196729](https://bugs.openjdk.java.net/browse/JDK-8196729) for the rmi communications port?
>>
>> We can specify RMI communication port with `--rmiport` in `jhsdb debugd`. It has been introduced in [JDK-8196751](https://bugs.openjdk.java.net/browse/JDK-8196751).
>
> For example, if we want to fix RMI registry and communication port, we can start debugd instance as following:
>
> $ jhsdb debugd --pid 1234 --registryport 2000 --rmiport 3000
>
> Then, we can connect to it as following:
>
> $ jhsdb jinfo --connect localhost:2000
Sorry. I was running an old jhsdb. So we already have --registryport 2000 --rmiport, and you can already specify [:<registryport>] as part of the debugserver. So what needs to be added is just --servernameprefix, and better help for explaining all the parts of the debugserver that are specified with --connect. You also want to add --disableregistry, but I think that's kind of separate from the above and probably needs its own CR and CSR.
-------------
PR: https://git.openjdk.java.net/jdk/pull/3000
More information about the serviceability-dev
mailing list