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/05 08:35:46 UTC
[jira] Created: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
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.
[jira] Commented: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] [Closed] (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Forrest Xia (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Forrest Xia closed GERONIMO-5749.
---------------------------------
Resolution: Fixed
Fix will be in 2.1.8 release
> 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: Shenghao Fang
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy updated GERONIMO-5749:
------------------------------------------
Attachment: (was: runsql.bat)
> 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.
[jira] [Assigned] (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Shenghao Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shenghao Fang reassigned GERONIMO-5749:
---------------------------------------
Assignee: Shenghao Fang (was: Vamsavardhana Reddy)
> 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: Shenghao Fang
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978293#action_12978293 ]
Vamsavardhana Reddy commented on GERONIMO-5749:
-----------------------------------------------
At revision: 1055843 on branches\2.1 (i.e. 2.1.8-SNAPSHOT).
o Added a deployer command to enable/disable stats query snapshot thread for Default Server.
> 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.
[jira] Updated: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy updated GERONIMO-5749:
------------------------------------------
Attachment: runsql.sh
runsql.bat
> 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.
[jira] Updated: (GERONIMO-5749) Command Line utility to
enable/disable Monitoring server and Stat query Snapshot thread for
DefaultServer
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ 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.