JMX Monitoring and the C3P0 connection pools

kasmith

I'd like to monitor c3p0 connection pools within my tomcat app. I've used the Component Wizard to create a template, and have assigned the monitors to the Existing Connection Pools. The problem is: When the tomcat server restarts, the ObjectName changes, and I lose monitoring on the attributes I require.

How does one get around this limitation?

aLTeReGo

Is this information present in any other location that does not change with each reboot? You could create your own MBean that presents this information in a persistent fashion. The only other way that comes to mind would be to create a script monitor if there was some logic you could script you could write that would determine where to fetch the information from.