jmx-dev RFR 6399961: The management agent doesn't support SSL keystore setup when loaded dynamically
Jaroslav Bachorik
jaroslav.bachorik at oracle.com
Tue Oct 1 06:03:35 PDT 2013
Ok, thanks everyone for taking time reviewing this. Dmitry's comment
about jcmd got me looking at the properties available when using the
jcmd to start the management agent.
It turns out that "com.sun.management.jmxremote.ssl.config.file" allows
exactly the thing this issue talks about.
So, please, disregard this change completely.
Cheers,
-JB-
On 1.10.2013 13:51, Dmitry Samersoff wrote:
> Jaroslav,
>
> Agent.java:
>
> 99:
>
> As far as you intorduce SSL_PREFIX constant, please add one for
> "com.sun.management."
>
> 259:
>
> It's better to keep all property manipulations in agentmain and
> startRemoteManagementAgent - different methods to start Agent might have
> separate property set and scoping rules.
>
> Do you need to modify jcmd as well?
>
> -Dmitry
>
>
> On 2013-10-01 13:01, Jaroslav Bachorik wrote:
>> Hi,
>>
>> Currently it is not possible to configure SSL parameters when loading
>> the management agent. The fix is to forward any javax.net.ssl.*
>> properties to the target JVM. The javax.net.ssl.* properties provided in
>> the agent configuration should never replace any javax.net.ssl.*
>> properties defined by the target JVM.
>>
>> The issue: https://bugs.openjdk.java.net/browse/JDK-6399961
>> Webrev: http://cr.openjdk.java.net/~jbachorik/6399961/webrev.00
>>
>> Thanks,
>>
>> -JB-
>
>
More information about the serviceability-dev
mailing list