Hi Chris,
Thank you for describing this in such details! Your description is correct.
In addition, apart from jstat there is jps tool that also can communicate
with jstatd and currently it faces the same problems if jstatd is deployed
behind
a firewall or in a container: after successful connec
Hi Daniil,
Just want to make sure I understand what communications are going on
here. Your concern is when the jstat and jstatd processes are on
different sides of the firewall. When you launch jstatd, you specify the
socket port it will receive requests on, and when you launch jstat, you
mus
Please review change [1] that adds a new command line option to jstatd tool to
specify a RMI connector port.
Currently a random port is used that prevents this tool from being used behind
a firewall or in a container.
New CSR [3] was created for this change and it needs to be reviewed as well.
Hi Vladimir,
thanks for looking at this and providing feedback.
I though as well about using a handshake there. I'll try it.
Thanks, Richard.
-Original Message-
From: Vladimir Ivanov
Sent: Donnerstag, 30. Januar 2020 17:55
To: Reingruber, Richard ;
serviceability-dev@openjdk.java.net
