]
Darran Lofthouse commented on REMJMX-78:
----------------------------------------
If you have a server you can not connect to please create a new Jira issue and also
include the server configuration. At this point I do not believe your assertion is
correct as Remoting JMX is used against clean builds of WildFly which do not have SSL
enabled.
Make XNIO and Remoting options be configurable
----------------------------------------------
Key: REMJMX-78
URL:
https://issues.jboss.org/browse/REMJMX-78
Project: Remoting JMX
Issue Type: Feature Request
Affects Versions: 1.1.0.Final
Environment: EAP 6.1.1
Reporter: Osamu Nagano
Assignee: Darran Lofthouse
Properties passed via "env" in "JMXConnectorFactory.connect(serviceURL,
env)" is very limited. And it is not passed to XNIO and Remoting like in line 192
below. It is more flexible if those are configurable like in jboss-ejb-client project.
https://github.com/jbossas/remoting-jmx/blob/1.1.0.Final/src/main/java/or...
{code}
191 final Xnio xnio = Xnio.getInstance();
192 endpoint = Remoting.createEndpoint("endpoint", xnio,
OptionMap.create(Options.THREAD_DAEMON, true));
193 endpoint.addConnectionProvider(CONNECTION_PROVIDER_URI, new
RemoteConnectionProviderFactory(), OptionMap.EMPTY);
{code}