[
https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978441#action_12978441
]
Vamsavardhana Reddy commented on GERONIMO-5749:
-----------------------------------------------
I have created two sql files enable-monitoring.sql, disable-monitoring.sql and
two command scripts runsql.bat, runsql.sh to run the sql by using the
org.apache.derby.tools.ij class. I have manually copied these four files over
to the bin directory and tested that the script run fine. I am thinking of
packaging these files in "mconsole-ds" project so that they get copied over to
the bin directory when the mconsole-ds plugin gets installed. Anybody has any
comments on whether this is ok or a suggestion on where to package these four
files?
> Command Line utility to enable/disable Monitoring server and Stat query
> Snapshot thread for DefaultServer
> ---------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5749
> URL: https://issues.apache.org/jira/browse/GERONIMO-5749
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Affects Versions: 2.1.7
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: 2.1.8
>
>
> Currently there is no command line utility to enable/disable Monitoring on
> Default Server and start/stop of Stats Query snapshot thread. The only way
> to do these operations is through Monitoring portlet in the admin console.
> Enable/disable Monitoring is done by changing ENABLED column in SERVERS and
> GRAPHS tables in MonitoringClientDB. SQL scripts can be provided for this to
> execute from command line.
> Start/Stop of snapshot thread is done by calling MasterRemoteControlJMX GBean
> methods. Ideal place to provide support for this would be through a new
> deployer command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
