monitoring doesn't start "not found: protocol"

[berenz]

I installed the java-monitor but it throws an exception:
Caused by: javax.management.AttributeNotFoundException: not found: protocol

I'm not really good with Jboss, any help much appreciated.


Here is the full error message:
2011-01-20 18:13:40,912 ERROR [STDERR] Jan 20, 2011 6:13:40 PM com.javamonitor.JavaMonitorCollector$CollectorDriv er run
SEVERE: This probe was hit by an unexpected exception: null
javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handl eInvocationExceptions(ReflectedDispatcher.java:180 )
at org.jboss.mx.interceptor.AttributeDispatcher.invok e(AttributeDispatcher.java:103)
at org.jboss.mx.server.Invocation.dispatch(Invocation .java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:86)
at org.jboss.mx.interceptor.ModelMBeanAttributeInterc eptor.invoke(ModelMBeanAttributeInterceptor.java:1 97)
at org.jboss.mx.interceptor.PersistenceInterceptor.in voke(PersistenceInterceptor.java:76)
at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:88)
at org.jboss.mx.server.AbstractMBeanInvoker.getAttrib ute(AbstractMBeanInvoker.java:362)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(M BeanServerImpl.java:556)
at com.javamonitor.JmxHelper.query(JmxHelper.java:210 )
at com.javamonitor.JmxHelper.query(JmxHelper.java:192 )
at com.javamonitor.JmxHelper.queryString(JmxHelper.ja va:102)
at com.javamonitor.Collector.push(Collector.java:128)
at com.javamonitor.JavaMonitorCollector$CollectorDriv er.run(JavaMonitorCollector.java:150)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.management.AttributeNotFoundException: not found: protocol
at org.jboss.mx.server.AbstractMBeanInvoker.getAttrib ute(AbstractMBeanInvoker.java:335)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(M BeanServerImpl.java:556)
at com.javamonitor.JmxHelper.query(JmxHelper.java:210 )
at com.javamonitor.JmxHelper.queryString(JmxHelper.ja va:120)
at com.javamonitor.mbeans.ServerTomcat.getHttpPort(Se rverTomcat.java:62)
at com.javamonitor.mbeans.Server.getHttpPort(Server.j ava:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.mx.interceptor.AttributeDispatcher.invok e(AttributeDispatcher.java:99)
... 13 more

[kjkoster]

Dear berenz,

First of all: welcome to Java-monitor.

Can you please tell me what version of JBoss you are using? There are a few strange things in your stack traces that I need to investigate. I'd like to reproduce this locally.

Kees Jan

[berenz]

Dear Kees Jan

thanks for your quick reply.

The Jboss version is: jboss-4.2.2.GA

berenz

[kjkoster]

Dear berenz,

After some investigation I found that our probe was looking at the wrong connector kinds (EJB connector mbeans don't have protocol and port attributes). I have updated the Java-monitor probe to be robust against this problem.

Please update your probe by downloading a a new one from Java-monitor.com and replacing the faulty one.

Thank you for posting this problem.

Kees Jan

[berenz]

Dear Kees Jan,

thanks a lot for fixing it. The probe is working!
Can't wait to look at the collected data.

Thanks again,
berenz

[kjkoster]

Dear berenz,

Outstanding. Happy hacking.

Kees Jan