Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 8.2.0.Final
    • Fix Version/s: None
    • Component/s: JMX
    • Steps to Reproduce:
      Hide

      1. Run 'sh jconsole.sh'
      2. Failure to connect remotely to a wildfly instance using http-remoting-jmx

      Show
      1. Run 'sh jconsole.sh' 2. Failure to connect remotely to a wildfly instance using http-remoting-jmx

      Description

      The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://

      {insert server ip here}

      :9990}} is probably never recognized and the connection is never done.

      The path, under mac is:

      /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar

      So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                avlemos André Lemos
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: