Do you have a more detailed error in jboss/log/server.log?
No I don't see anything in server.log. I think that the JMX HTML Adapter is catching the runtime exception and does not output any log.
The only thing I can suggest is debugging.
If you have the source, you could wrap the whole
method in an exception handler then
log.error() any unhandled exception.
What jndi bindings do you have specified in the ear?
You are encountering a known bug in the JNDIView MBean. The bug was patched in December, but the patch was not incorporated into the 2.4.4 release.
Do what I did: fetch the latest copy of JNDIView.java and JNDIViewMBean.java from Sourceforge. Change the package name to com.mycompany.*, then build and deploy onto your server.
Now, edit your jboss.jcml file so that the JNDIViewMBean is instantiated from com.mycompany...JNDIView instead of org.jboss...JNDIView, and you have a working JNDIView under 2.4.4.