Dec 12th, 2007, 09:43 AM
JMX config on Websphere
I wish to a expose a number of Spring managed CronTriggerBean's so we are able to change the rate at which jobs are scheduled.
On Websphere 6.0 if I deploy a simple MBean Spring 1.2 configuration (MBeanExporter listing bean name/value pairs) I continually get InstanceAlreadyExistsException's even when deploying for the first time with a new MBean name....
This problem seems to go if I create my own Mbean server (via MBeanServerFactoryBean) in as much as I get no errors in the server log when deploying - this doesn't feel right, surely I should be using something existing within Websphere ?
As a side question - I was assuming I'd be able to view and administer the Mbeans using a browser out of the box (like say the CruiseControl admin console) after exposing the beans. A quick read around suggests I would need to use MC4J, JConsole or some third party servlet based solution - is this the case or am I missing something ?