Hi Jay,
I renamed the artifact but the issue persists.
2012-01-16 18:02:38,387 WARN [ResourceContainer.invoker.daemon-1]
(org.rhq.plugins.jbossas.JBossASServerComponent)- Could not establish
connection to the JBoss AS instance [121] times for resource
[/usr/local/jboss/server/default]
org.mc4j.ems.connection.EmsConnectException:
java.io.StreamCorruptedException:
javax.management.MalformedObjectNameException:
jboss.j2ee:ear=srh-businesscore.ear,jar=srh-businesscore-ejb-1.5.3-SNAPSHOT.jar,name=,service=EJB3
is not a valid ObjectName. Invalid key/value data name
at
org.mc4j.ems.impl.jmx.connection.support.providers.proxy.GenericMBeanServerProxy.invoke(GenericMBeanServerProxy.java:156)
at $Proxy55.queryNames(Unknown Source)
at
org.mc4j.ems.impl.jmx.connection.DConnection.loadSynchronous(DConnection.java:138)
at
org.rhq.plugins.jbossas.JBossASServerComponent.loadConnection(JBossASServerComponent.java:1122)
I had asked the developer about the "name" key to empty value, but he too
could not help.
I'm using RHQ 4.1 and the JBoss community server version is 4.2.1 G.A.
Thank you.
2012/1/16 Jay Shaughnessy <jshaughn(a)redhat.com>
I don't think it likes the "name=" portion of the mbean name. That needs a
value. I'm not sure why it doesn't have a value but maybe it's having
trouble parsing the ear file name "srh-businesscore-ear.ear". That should
be valid I think, but perhaps the "ear" in name part is causing a problem.
maybe rename the ear and see if that solves the problem. If so, please let
us know as that's probably a bug.
If not, let us at least know the RHQ and app server version you're working
with.
On 1/16/2012 2:27 PM, Herbert de Borba wrote:
>
> Hello all, it's my first post to this list, don't know if this is the
> right place for the question, but I can't find any references to this issue
> on the web, so there it goes...
>
> I have a RHQ server that's already working with several agents and is
> monitoring some EJBs/EARs between other resources. But when I try to start
> this specific agent the log reports this error (agent.log):
>
> <pre>
> 2012-01-16 16:09:59,818 WARN [ResourceContainer.invoker.**daemon-1]
> (org.rhq.plugins.jbossas.**JBossASServerComponent)- Could not establish
> connection to the JBoss AS instance [11] times for resource
> [/usr/local/jboss/server/**default]
> org.mc4j.ems.connection.**EmsConnectException: java.io.**StreamCorruptedException:
> javax.management.**MalformedObjectNameException: jboss.j2ee:ear=srh-**
> businesscore-ear.ear,jar=srh-**businesscore-ejb-1.5.3-**
> SNAPSHOT.jar,name=,service=**EJB3 is not a valid ObjectName. Invalid
> key/value data name
> at org.mc4j.ems.impl.jmx.**connection.support.providers.**
> proxy.GenericMBeanServerProxy.**invoke(**GenericMBeanServerProxy.java:**
> 156)
> at $Proxy55.queryNames(Unknown Source)
> at org.mc4j.ems.impl.jmx.**connection.DConnection.**
> loadSynchronous(DConnection.**java:138)
> ...
> </pre>
>
>
> The agent then is unable to report the correctly running JBossAS to the
> RHQ server and it shows it as if the JBossAS is down, what is not the case
> since the AS is up and the services it serves are working.
>
> If I undeploy this EAR the problem disapear.
>
> Does someone has any tips on what's going on? What's that name it is
> expecting?
>
> Regards.
>
> --
> Herbert Mattei de Borba
> herbertdeborba(a)gmail.com
<mailto:herbertdeborba@gmail.**com<herbertdeborba@gmail.com>
> >
>
>
>
> ______________________________**_________________
> rhq-users mailing list
> rhq-users(a)lists.fedorahosted.**org <rhq-users(a)lists.fedorahosted.org>
>
https://fedorahosted.org/**mailman/listinfo/rhq-users<https://fedoraho...
>
______________________________**_________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.**org <rhq-users(a)lists.fedorahosted.org>
https://fedorahosted.org/**mailman/listinfo/rhq-users<https://fedoraho...
--
Herbert Mattei de Borba
herbertdeborba(a)gmail.com