Hi again, I have come across some weird(seeming) problem. In my ActiveBPEL discovery component, I connect to the JMX server on my Tomcat instance to look up the existence of a bean and extract a value from it, like so: private final static String AE_WEBMODULE_BEAN = "Catalina:j2eeType=WebModule,name=//localhost/active-bpel,J2EEApplication=none,J2EEServer=none"; .... EmsConnection connection = null; try { connection = context.getParentResourceComponent().getEmsConnection(); EmsBean testBean = connection.getBean("Catalina:type=Server"); String testPort = testBean.getAttribute("port").getValue().toString(); log.debug(LOG_PREFIX + "THE PORT BEAN: " + testPort); log.debug(LOG_PREFIX + "CONNECTION URL: " + connection.getConnectionProvider().getConnectionSettings().getServerUrl()); EmsBean bean = connection.getBean(AE_WEBMODULE_BEAN); String aePath = bean.getAttribute("path").getValue().toString(); The poor agent ends up complaining as follows: EmsException: Could not load attribute value null. Now, the same code works for retrieving a very similar MBean for Axis, the ActiveBPEL MBean name I'm using seems to be okay, testPort above is as expected. Why would it not be able to get the bean and its attributes? Has anyone come across this in a similar context? I have read something about a Jopr/RHQ bug that results in the same exception... Thanks, -- Bruno