4 Replies Latest reply on Sep 17, 2012 9:53 AM by Johan Vermeij

    JBoss jdr.sh diagnostic utility

    Johan Vermeij Newbie

      I would like to have a look at the output produced by jdr.sh

       

      I run jdr.sh --host xxx.xxx.xxx.xxx

       

      Output in the sos.txt report:

      -  files created:

        * configuration.json

        * dump-services.json

        * cluster-proxies-configuration.json

        * threaddump.json

      -  alerts:

        ! INFO: The JBoss installation directory supplied to SOS is /usr/share/JBoss/jboss-eap-6.0

        ! JBOSS API call failed, falling back to HTTP: Controller Client is not available

        ! Could not query url: http://localhost:9990/management; error: <urlopen error (111, 'Connection refused')>

        ! JBOSS API call failed, falling back to HTTP: Controller Client is not available

        ! Could not query url: http://localhost:9990/management; error: <urlopen error (111, 'Connection refused')>

        ! JBOSS API call failed, falling back to HTTP: Controller Client is not available

        ! Could not query url: http://localhost:9990/management; error: <urlopen error (111, 'Connection refused')>

        ! JBOSS API call failed, falling back to HTTP: Controller Client is not available

        ! Could not query url: http://localhost:9990/management; error: <urlopen error (111, 'Connection refused')>

       

      jdr.sh somehow always tries to connect to the controller on localhost

       

      How can I force it to look at the controller on xxx.xxx.xxx.xxx:9990 ?