JBoss jdr.sh diagnostic utility

[johanvermeij]

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 ?

[nickarls]

Looking at https://github.com/jbossas/jboss-as/blob/master/jdr/jboss-as-jdr/src/main/java/org/jboss/as/jdr/CommandLineMain.java one gets the impression it should work. What version are you on?

I tried on windows and managed to get different results when I applied the --host --port parameters. On 7.1.1 the windows-script might have been broken as I got a Unrecognized option: -Djboss.home.dir=...

[johanvermeij]

I am using eap 6 under Centos 6 Linux

I will try 7.1.1 tonight and post the result here

-------------

I get the same result with 7.1.1 under Centos 6

I will try under Windows tomorrow

[jbertram]

Johan, if you are using EAP 6 then you should really be leveraging the professional support which Red Hat offers for its products.  If there is a bug then you should be able to get a patch for it.  If you implement fixes from the community then you will comprimise the supportability of your environment.

[johanvermeij]

Thanks Justin

Point taken