HP Diagnostics and AS 7

[bill.rosenberg]

Has anyone had success using HP Diagnostics version 9.2 and AS 7? We had previously used the diagnostics tool with JBOSS 4.0.2 and had the tool show good diagnostics metrics, but with AS 7 it only shows the memory used by the JVM and not all the metrics i am used to such as SQL logging, server requests, connection pool monitoring etc.

Thanks,

Bill

[wdfink]

I suppose that the HP diagnostic rely on JMX Bean's.

AS7 use a different way for management, so you are not able to get such information with JMX

[marco.battaglia]

You can monitoring jboss as 7 using jmx protocol:

1) [optional in order to use port 4447 instead of 9999] add attribute use-management-endpoint="false" to connector element of remoting subsystem

2) from /bin folder lauch ./add-user.sh or .bat in order to add a user under management realm (jmx remoting is secured by management realm)

3) in your /bin folder there is a ./jconsole.sh (check if our JAVA_HOME is setted ) launch ./jconsole.sh

4) to connect set:

-remote: true

-in the textfield add: "service:jmx:remoting-jmx://[host]:4447" where host is the ip or logicalname of the binding address of the jboss as 7 to monitor

-user: username just created

-password_password just setted

you can also monitor jboss using wget on RESTApi of cli:

for example:

wget -O result.txt "http://admin:pswd@localhost:9990/management/subsystem/datasources/data-source/ExampleDS/statistics?read-resource&include-runtime=true&recursive&json.pretty" 

Try also with:

./jboss-cli.sh --connect --command=”/core-service=platform-mbean/type=threading:dump-all-threads(locked-monitors=true, locked-synchronizers=true)”

In these days I'm going to use HP and I'll report you how to do. Consider also RHQ it is really better than previous versions.

Bye