You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2011/01/06 19:59:47 UTC
[jira] Updated: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy updated GERONIMO-5749:
------------------------------------------
Attachment: runsql.bat
disable-monitoring.sql
enable-monitoring.sql
> 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
>
> Attachments: disable-monitoring.sql, enable-monitoring.sql, runsql.bat
>
>
> 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.