Added feature: custom jmx protocol connection (aragozin#17)

Now supports Wildfly's http-remoting jmx protocol.

Sample in-shell usage with wildfly client jars:

LIB_DIR="${WILDFLY_HOME:-/opt/wildfly}/bin/client"
JMX_PROTO="http-remoting-jmx"

java \
  -Djmx.service.protocol=${JMX_PROTO} \
  -Djava.ext.dirs=${LIB_DIR} \
  -jar "/opt/jvm-tools/sjk-plus.jar" $@

Author: kyxap1

JMX-HTTP.md

@@ -0,0 +1,15 @@
+WildFly application service support proprietary
+JMX over HTTP transport.
+
+Below is example shell script to let SJK use JMX over HTTP instead of JMX over RMI transport.
+Additional WildFly client jars are required.
+
+	#!/usr/bin/env bash
+	set -eu
+	LIB_DIR="${WILDFLY_HOME:-/opt/wildfly}/bin/client"
+	JMX_PROTO="http-remoting-jmx"
+
+	java \
+	  -Djmx.service.protocol=${JMX_PROTO} \
+	  -Djava.ext.dirs=${LIB_DIR} \
+	  -jar "/opt/jvm-tools/sjk-plus.jar" $@

sjk-core/src/main/java/org/gridkit/jvmtool/JmxConnectionInfo.java

@@ -99,7 +99,12 @@ else if (sockAddr != null) {
 	@SuppressWarnings("resource")
 	private MBeanServerConnection connectJmx(String host, int port, Map<String, Object> props) {
 		try {
-			final String uri = "service:jmx:rmi:///jndi/rmi://" + host + ":" + port + "/jmxrmi";
+                        String proto = System.getProperty("jmx.service.protocol", "rmi");
+
+                        final String uri = "rmi".equals(proto) ?
+                          "service:jmx:rmi:///jndi/rmi://" + host + ":" + port + "/jmxrmi" :
+                          "service:jmx:" + proto + "://" + host + ":" + port;
+                  
 			JMXServiceURL jmxurl = new JMXServiceURL(uri);						
 			JMXConnector conn = props == null ? JMXConnectorFactory.connect(jmxurl) : JMXConnectorFactory.connect(jmxurl, props);
 			// TODO credentials