RFR: 8316649: JMX connection timeout cannot be changed and uses the default of 0 (infinite)

[Daniel Fuchs]

On Thu, 23 Nov 2023 17:17:34 GMT, Daniel Fuchs <dfuchs at openjdk.org> wrote:

>>>  I see Integer.getInteger handles the obvious Exceptions, so specifying a strange value does not immediately break us.
>> 
>> Oh - right. It's `Integer.getInteger`, not `Integer.parseInt` Ok, then - I withdraw my first comment :-)
>
>> This is a stack from a test I was experimenting with, when it did see the timeout:
> 
> Ah - that's for testing with a particular test. So the question now is:
> 
> Should the RMISocketFactories provided / implemented in the JMX implementation - such as those used by the JMX default agent, also honour this system property?

(Look for socket factories in the module `jdk.management.agent`)

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/16771#discussion_r1403622189