You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2014/12/20 20:52:51 UTC
[Bug 57377] Incorrect use of standard SSL properties for JMX in
JMXRemoteLifecycleListener
https://issues.apache.org/bugzilla/show_bug.cgi?id=57377
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
(In reply to Ravi Sanwal from comment #0)
> Would it be possible to have separate RMIServerSocketFactory for JMX/RMI and
> RMI registry, one dictated by com.sun.management.jmxremote.ssl (which
> results in the rmiSSL flag) and the other by
> com.sun.management.jmxremote.registry.ssl.
That seems like a reasonable request.
> This way the agent will be more compliant and we'd still have the ability to
> leave the RMI registry non SSL (which is to get the JMX/RMI connection stub).
>
> We can also fix the "rmiBindAddress incompatible with rmiSSL" problem by
> creating a custom SslRMIServerSocketFactory (basically extending the one in
> JDK and re-implementing the createServerSocket method to use the given
> rmiBindAddress.
>
> I'd be happy to do these changes, and can provide the changed version of
> this file, if this request seems reasonable. May be a patch as well if I
> learn SVN quickly.
A patch in diff -u format is preferred. Failing that the new version based on
the latest trunk version would be fine.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org