My JBoss AS JVM services are shown as DOWN when they are UP

[mzeijen]

I have a Jopr 2.2.0 installation that monitors several JBoss AS servers. When those servers are all up and running then most of the time the JBoss AS JVM services are shown as DOWN. Some times, after a while, they show as UP. I don't understand why they show as DOWN and I even less understand why, after a while, they show as UP. What could be wrong?

[mazz]

If they NEVER went green, I would be tempted to say you didn't pass "-Djboss.platform.mbeanserver" to the JbossAS instance.

But since you say they magically turn green after a while, I'll have to ask a couple of things:

a) how soon after you either start the agent or the JBossAS server do they go from red to green? (1 minute? 30 minutes? random?)

b) does the availability waffle between green and red randomly? or does it stay green once it reaches green? (assuming the JbossAS server remains up, of course).

c) look in your agent's log file (<rhq-agent-install>/logs) and see if you can see any errors that might indicate a problem

[mzeijen]

"mazz" wrote:
If they NEVER went green, I would be tempted to say you didn't pass "-Djboss.platform.mbeanserver" to the JbossAS instance.

I pass the "-Djboss.platform.mbeanserver" to the JbossAS instance, so that can't be the problem. But two other relating lines are the probably the problem. I get back to that at the end of the post.

"mazz" wrote:

a) how soon after you either start the agent or the JBossAS server do they go from red to green? (1 minute? 30 minutes? random?)

It is a bit random. One server is green and it's 'clone' server is still red.

"mazz" wrote:

b) does the availability waffle between green and red randomly? or does it stay green once it reaches green? (assuming the JbossAS server remains up, of course).

When it is green it stays green.

"mazz" wrote:

c) look in your agent's log file (<rhq-agent-install>/logs) and see if you can see any errors that might indicate a problem

I couldn't find anything that is related. There is only this strange exception:

2009-05-07 16:24:04,859 WARN [MeasurementManager.collector-1] (rhq.core.pc.measurement.MeasurementCollectorRunner)- Failure to collect measurement data from: org.rhq.plugins.jbossas.JBossMessagingComponent@8f7f42
java.lang.IllegalStateException: EMS bean was null for Resource with type [ResourceType[id=0, category=Service, name=JBM JMS Queue, plugin=JBossAS]] and key [jboss.messaging.destination:name=testDistributedQueue,service=Queue].
 at org.rhq.plugins.jmx.MBeanResourceComponent.getEmsBean(MBeanResourceComponent.java:132)
 at org.rhq.plugins.jmx.MBeanResourceComponent.getValues(MBeanResourceComponent.java:225)
 at org.rhq.plugins.jbossas.AbstractMessagingComponent.getValues(AbstractMessagingComponent.java:118)
 at org.rhq.plugins.jbossas.JBossMessagingComponent.getValues(JBossMessagingComponent.java:66)
 at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
 at java.util.concurrent.FutureTask.run(FutureTask.java:123)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)

That one probably has nothing to do with my current problem.

But I believe that I found the problem. I had the following three lines in my JBoss run script (windows)

set JAVA_OPTS=%JAVA_OPTS% -Djboss.platform.mbeanserver
set JAVA_OPTS=%JAVA_OPTS% -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote

When I 'rem' (comment out) the last two lines than the problem is solved. When I put them back in then the problem is back.

[rafaelcba]

I had the same problem but just the "-Djboss.platform.mbeanserver" was sufficient fror me. I'm using OS Linux.

Really without this JVM param. the JBoss AS monitoring isn't possible. IMHO I think this configuration could be more highlighted on Doc pages... I this it's only found on JON's faq page.

[mazz]

"without this JVM param. the JBoss AS monitoring isn't possible."

that isn't entirely true... without that you cannot monitor the "JVM" MBeans (the Memory Subsystem MBean, etc). But you can still get JBossAS MBean information (datasource monitoring, EJB monitoring, etc)