> > Internal database tables created by H2 that > > provide monitoring data? > > Yes, if the server is running, there is an internal in-memory > database... But the monitoring application would need to run in the > same virtual machine. Probably JMX would be the 'correct' solution, > right?
As Joe said, we can do whatever you give us access to :) It doesn't have to be JMX. If this internal in-memory database is accessible to us through JDBC access using SQL queries, that's just as good as JMX (we do this same kind of thing when monitoring Oracle - we query the V $STATISTICS table and the like to obtain monitoring data). If you are saying this internal in-memory database is not externally accessible, then yes, JMX would be the "most-correct" solution. You could expose your management data as a set of MBeans that expose the internal in-memory data. To start (if you haven't done any of this yet) is to just use the platform MBeanServer ( http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ManagementFactory.html#getPlatformMBeanServer() ) and rely on standard JMX remoting and we can tunnel through that to your MBeans. See: http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html . --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
