mraccola
Apr 27th, 2006, 09:52 PM
I am having a terrible time getting my beans exported into WebSphere's MBean server. I am using WAS 5.1.1 with PARENT_LAST class loader mode.
When I try using MBeanExporter without specifying a server, I get a stack trace saying no MBean server was found. When I setup an MBeanServerFactoryBean in Spring and supply that to the MBeanExporter then the bean is not found in the WAS MBeanServer, so it seems like the beans were exported to a brand new MBean server (not the embedded WAS MBean server).
I went down the route of writing a WebSphere-specific MBeanServerFactoryBean, similar to the WebLogicMBeanServerFactoryBean, but to no avail, I end up with a ClassCastException.
I believe I know what the problem is, but its just a hunch. I am using Hibernate with JBoss TreeCache. JBoss TreeCache requires you to include a version of the javax.management classes in order for use (even though JMX is not used when not deploying in a JBoss container). The version of these classes appears to conflict with the WAS version. So, I'm in a catch 22. JBoss won't accept WAS version, WAS won't accept JBoss version.
Can anyone confirm this? I saw a JIRA issue on reducing the JBoss TreeCache dependencies, but no activity...any workaround other than switching to a different cache?
When I try using MBeanExporter without specifying a server, I get a stack trace saying no MBean server was found. When I setup an MBeanServerFactoryBean in Spring and supply that to the MBeanExporter then the bean is not found in the WAS MBeanServer, so it seems like the beans were exported to a brand new MBean server (not the embedded WAS MBean server).
I went down the route of writing a WebSphere-specific MBeanServerFactoryBean, similar to the WebLogicMBeanServerFactoryBean, but to no avail, I end up with a ClassCastException.
I believe I know what the problem is, but its just a hunch. I am using Hibernate with JBoss TreeCache. JBoss TreeCache requires you to include a version of the javax.management classes in order for use (even though JMX is not used when not deploying in a JBoss container). The version of these classes appears to conflict with the WAS version. So, I'm in a catch 22. JBoss won't accept WAS version, WAS won't accept JBoss version.
Can anyone confirm this? I saw a JIRA issue on reducing the JBoss TreeCache dependencies, but no activity...any workaround other than switching to a different cache?