Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't monitor webapp's JVM in JBoss EAP 6.2 (Domain mode) #34

Closed
ranmses opened this issue Jan 30, 2015 · 2 comments
Closed

Can't monitor webapp's JVM in JBoss EAP 6.2 (Domain mode) #34

ranmses opened this issue Jan 30, 2015 · 2 comments

Comments

@ranmses
Copy link

ranmses commented Jan 30, 2015

Hello,
For the last couple of days I've been trying to monitor all the JVM's in our JBoss system.
We have 3 working VM (CentOS 6.5) in domain mode (1 master + 2 slaves).
As I type, that's the current situation:

  • Master: 2 JVM processes, 1 host controller + 1 process controller

  • Slave 1 : 3 JVM processes, 1 host controller + 1 process controller + 1 webapp (deployed jar)

  • Slave 2 : 3 JVM processes, 1 host controller + 1 process controller + 1 webapp (deployed jar)
    There' s one jmxetric xml file for each JVM. The problem:

    We cannot make the webapp JVM's to be monitored. The 6 others are correctly monitored.

For each one of the xml files I uncommented the lines below:

           <mbean name="jboss.as:subsystem=web,connector=ajp" pname="ajp">
                  <attribute name="requestCount" type="int32" slope="positive"/>
           </mbean>

All JVM processes show references of oncrpc-1.0.7.jar, gmetric4j-1.0.7.jar and jmxetric-1.0.6.jar, with apparently correct configurations. Tried to increase the delay at the xml file, but no luck.

Any ideas?

Best!

@dpocock
Copy link
Member

dpocock commented Jan 31, 2015

This Github bug tracker is only used for tracking confirmed bugs.

This looks more like a "how do I?" support request, please ask on the ganglia-general mailing list or possibly the JBoss user forum.

Two suggestions I can make:

  • check you have a distinct for each JVM on the same host, if two JVMs are on the same host they must not use the same process name there.
  • use lsof to check the JVM process to see if the jmxetric code opened a socket

@ranmses
Copy link
Author

ranmses commented Jan 31, 2015

Ok, sorry for the wrong request.

Yes, there's one xml with a unique process name for each JVM. I already have 2 different JVM being monitored at each one of the 3 hosts.

The problem is with the third JVM, which supports a webapp from a deployed jar file.

Will check if the socket is being open, but I suppose not since there's no sign of the metric with 'telnet localhost PORT'.

Well, thank you anyway.

@ranmses ranmses closed this as completed Jan 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants