[
https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980017#action_12980017
]
Vamsavardhana Reddy commented on GERONIMO-5749:
-----------------------------------------------
At revision: 1057539 on branches\2.1 (i.e. 2.1.8-SNAPSHOT).
o Added SQL scripts to enable/disable monitoring on Default Server
o Added Windows and Unix batch files to execute SQL using ij from Derby
o Files will be copied to server's bin directory when the plugin is installed.
o Eg. script to enable monitoring:
runsql localhost 1527 dbadmin manager enable-monitoring
> 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, runsql.sh
>
>
> 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.
