Reason for Error "EMS bean was null for Resource with type JBossAS"

[ssroy73]

Hi,

I am almost continously getting following error.

2010-08-04 12:57:41,566 DEBUG [InventoryManager.availability-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Call to [org.rhq.plugins.jbossas.JBossASTomcatConnectorComponent.getAvailability()] with args [] failed.
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: EMS bean was null for Resource with type [ResourceType[id=0, category=Service, name=Connector, plugin=JBossAS]] and key [jboss.web:address=ssroy.com%2F127.0.0.1,port=8009,type=Connector].
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232)

Can anyone please let me know the reason for this error.

Following are the environment details.

OS: Ubuntu Linux
JBoss: 4.2.3
Apache: 2.2.15
RHQ 3
DB: Oracle 10g
JDK: 1.6.0_20

Thanks for your help.

Best Regards - Roy

[mazz]

don't know, but see if the MBean jboss.web:address=ssroy.com%2F127.0.0.1,port=8009,type=Connector really exists (if you have jmx-console in the JBossAS Server you can use that). Perhaps there was a service that was discovered and in the RHQ inventory but is no longer deployed in your JBossAS Server (particularly, this is a Tomcat connector listening on port 8009).

You can try to restart the agent with the "--purgedata" command line option - this will delete the agent-side inventory and force the agent to download/sync the inventory with the server.

[mazz]

BTW: this is logged at the DEBUG level, so that tells me this might not actually be an error condition. Its happening during the Availability check, so perhaps that connector is just not deployed and thus is to be considered DOWN by RHQ. I'm not sure, but it struck me that this was logged a DEBUG level, which tells me the develop might not consider this an error, but rather a common occurence.

[ips]

Did restarting the Agent as John Mazz suggested clear up the issue? Did you check jmx-console or twiddle to see if there is an MBean deployed with the name "jboss.web:address=ssroy.com%2F127.0.0.1,port=8009,type=Connector"?

Is this the final release of RHQ 3.0.0 or one of the B0x releases?

[ssroy73]

I tried as John suggested but still getting the same error.

I have also checked from jmx-console and found "jboss.web:address=ssroy.com%2F127.0.0.1,port=8009,type=Connector" is present.

I am using stable version 3.0.0.

Also none of the ServerInfo metrics are visible.

Any help will be greately appreciated.

Thanks & Regards - Roy

[ssroy73]

Hi,

I have overlooked something.

When I view from jmx-console, it shows

jboss.web:address=/127.0.0.1,port=8009,type=Connector

But from RHQ, it looks for

jboss.web:address=ssroy.com%2F127.0.0.1,port=8009,type=Connector

The above RED colour highlighted portion is not present in jmx-console and this could be reason of error. Is it possible to remove this error.

Also, I am not sure why I am getting different "ServerInfo" metrics values in jmx-console and RHQ. Any help will be greately appreciated.

Thanks a lot.

Best Regards,

Roy