Jconsole

[dpeddi]

Do you think it would be possible to use visualwas plugin with jconsole?

Found, to make visualwas visible to jconsole is enough to create:
META-INF\services\javax.management.remote.JMXConnectorProvider:
com.github.veithen.visualwas.jmx.soap.ClientProvider

Regards

[veithen]

The project already implements a JMX connector provider. To use it with JConsole, you would need to:

• Add the relevant JAR(s) to the classpath (on the issue-1 branch I added a Maven plugin invocation to build an all-in-one JAR so that you'd only need a single JAR).
• Set the jmx.remote.protocol.provider.pkgs system property to com.github.veithen.visualwas.jmx.
• Use service:jmx:soap://<host>:<port> as JMX URL.

[dpeddi]

Thank you, after some study I've reached the same result!

I think you can close this issue.

[veithen]

Did you make it work? Would you mind sharing your findings so we could document it?

[dpeddi]

Is possible to use visualwas with jconsole (or with plain java) by taking the nbm file, unpacking all jar and by putting them somewere. then start jconsole by creating a bat or a sh script like: set CLASSPATH=%JAVA_HOME%\lib\tools.jar set CLASSPATH=%CLASSPATH%;%JAVA_HOME%\lib\jconsole.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\jboss-client.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\axiom-api.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\axiom-impl.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\com-github-veithen-visualwas.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\commons-codec.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\commons-logging.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\connector.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\loader.jar set CLASSPATH=%CLASSPATH%;%JAR_HOME%\lib\org.eclipse.osgi.jar %JAVA_HOME%\bin\jconsole -debug -J-Djava.util.logging.config.file=%JAR_HOME%\logging.properties -J-Djava.security.properties=%JAR_HOME%\etc\java.security -J-Djava.class.path=%CLASSPATH% -J-Djmx.remote.protocol.provider.pkgs=com.github.veithen.visualwas.jmx.soap service:jmx:soap://yourserver:yourport (you can repack “connector.jar” a file META-INF\services\javax.management.remote.JMXConnectorProvider containing “com.github.veithen.visualwas.jmx.soap.ClientProvider” instead of putting -Djmx.remote.protocol.provider.pkgs) if you want to add more plugin like jboss-client.jar you need to concatenate the package where is redefined the ConnectorClient class. with "|" or repack connector.jar (you don't need any more to export the property.) About the ssl certificate, if you have a linux system you could do something like this # openssl s_client -showcerts -servername yourserver -connect yourserver:yourport< /dev/null > /etc/pki/ca-trust/source/anchors/yourserverhostname.pem # update-ca-trust extract (I'm sure there are other nicer ways but for now is ok for me) The same trick is applicable for any java program that use jmx with a configurable jmx endpoint. Regards

…

On Thu, Mar 8, 2018 at 12:28 AM, Andreas Veithen ***@***.***> wrote: Did you make it work? Would you mind sharing your findings so we could document it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCVX0rhLr1gDiQoXSHMIMvwTR6HwP6oks5tcG0GgaJpZM4SZzU9> .