[
https://issues.apache.org/jira/browse/QPID-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662332#action_12662332
]
Rob Godfrey commented on QPID-1517:
-----------------------------------
Comments on r732340 and r732729 which I believe is for this change:
Code seems fine after changes - Generally I dislike putting passwords on the
command line - can the CLI take them in via stdin? If so this would be a
preferable approach (and take via stdin for the script itself if not provided
on the cmdline)
> Create scripts (bat & bash) to set alerting configured value to that provided
> in config after broker startup
> ------------------------------------------------------------------------------------------------------------
>
> Key: QPID-1517
> URL: https://issues.apache.org/jira/browse/QPID-1517
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Aidan Skinner
>
> 1. Provide 2 scripts for a) running on linux & solaris (test on both) and b)
> running on windows
> 2. Intended that script run from a crontab/scheduler entry so should generate
> output to a log file if any errors (i.e. invalid config etc)
> 3. Script set all value as per the broker load i.e. set defaults for all new
> queues etc ?
> 4. Test that this works by setting thresholds very low and triggering the
> alerts, for all possible alert types
> 5. Ensure that scripts cannot bring broker down
> 6. Scripts will be released independently i.e. not make any assumptions about
> relative dir etc
> 7. Scripts should read the existing broker config file to get the threshold
> values to be used - probably need this as a parm for the script ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
