1 Reply Latest reply on May 5, 2016 6:32 AM by Martin Cassidy

    Is it possible to connect to wildfly with Java mission control ? and if so, How ? thanks.

    Alon Kaftan Newbie



      I am trying to connect JMC to wildfly, with no success

      I tried following the instructions here https://community.oracle.com/thread/2592885

      But it doesn't seems to work.

      should it be possible for these two to connect ? and if so, what should I do to make it work ?




        • 1. Re: Is it possible to connect to wildfly with Java mission control ? and if so, How ? thanks.
          Martin Cassidy Newbie

          I had the same problem and attempted to paste in the -Xbootclasspath from the answer supplied, adding my jboss path which didn't work for me either.


          I was able to get it working another way however. I updated jconsole.bat in [wildfly home]/bin directory, replacing the first line with @echo=on When running the bat, I then got the output I needed for jmc. Which for me looked like this:


          D:\Containers\wildfly\bin>if "" == "" ("C:\Program Files\Java\jdk1.8.0_40\bin\jco

          nsole.exe" "-J-Djava.class.path=C:\Program Files\Java\jdk1.8.0_40\lib\jconsole.j

          ar;C:\Program Files\Java\jdk1.8.0_40\lib\tools.jar;D:\Containers\wildfly\bin\clie

          nt\jboss-cli-client.jar" )  else ("C:\Program Files\Java\jdk1.8.0_40\bin\jconsol

          e.exe" "-J-Djava.class.path=C:\Program Files\Java\jdk1.8.0_40\lib\jconsole.jar;C

          :\Program Files\Java\jdk1.8.0_40\lib\tools.jar;D:\Containers\wildfly\bin\client\j

          boss-cli-client.jar"  )


          I then took the value of java.class.path which I pasted into jmc.ini as Xbootclasspath, which then looked like this:


          -Xbootclasspath/a:C:\Program Files\Java\jdk1.8.0_40\lib\jconsole.jar;C:\Program Files\Java\jdk1.8.0_40\lib\tools.jar;D:\Containers\wildfly\bin\client\jboss-cli-client.jar


          This will obviously be slightly different on your system, but if you use the output from jconsole.bat, it should be right.


          Once I had done that, I was able to connect using the normal wildfly service URL:




          Do make sure you've also added -XX:+UnlockCommercialFeatures to your JVM args and restarted as well, you won't be able to connect otherwise.

          1 of 1 people found this helpful