[
https://issues.apache.org/jira/browse/VCL-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252135#comment-14252135
]
ASF subversion and git services commented on VCL-758:
-----------------------------------------------------
Commit 1646521 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1646521 ]
VCL-758 - VCL timings - make various timings to be variables and edited by admin
states.php: (all changes to $actions['classmapping']
-changed timeoutvariable to timevariable
-removed duplicate entry for connectedusercheck
-changed connect to initialconnecttimeout
-changed reconnect to reconnecttimeout
siteconfig.php:
-class name changes: connect -> initialconnecttimeout; reconnect ->
reconnecttimeout
-name changes affected generalOptions and __construct for each class
-modified TimeVariable class to include $minval; affected __construct, getHTML,
AJaddAFfiliationSetting, and AJupdateAllSettings; set minval to 0 for
connectedUserCheck
siteconfig.js:
-modified addAffiliationSettingCBextra: set min constraint to data.items.mainval
-class name changes: connect -> initialconnecttimeout; reconnect ->
reconnecttimeout
> VCL timings - make various timings to be variables and edited by admin
> -----------------------------------------------------------------------
>
> Key: VCL-758
> URL: https://issues.apache.org/jira/browse/VCL-758
> Project: VCL
> Issue Type: Improvement
> Components: database, vcld (backend), web gui (frontend)
> Reporter: Aaron Peeler
> Priority: Minor
> Fix For: 2.4
>
>
> Allow VCL admins edit some of the timing values via the front-end.
> Possible variables to allow edits are:
> acknowledge timeout = time limit to wait on user to hit connect button
> connect timeout = wait for user to connect for normal reservations
> ignore_connections_gte = skip checks for durations gte X (24hrs is hardcoded
> in code)
> general_inuse_check = how often to check on normal reservations
> server_inuse_check = how often to check on server reservations
> cluster_inuse_check = how often to check on cluster reservations
> Some of these can easily be setup based on an affiliation, but others we may
> want to limit as a global setting such as general_inuse_check.
> Need a page on the web portal for admins to set the values.
> List of times for variable table and their default times being set in backend:
> acknowledgetimeout => '900',
> connecttimeout => '900',
> wait_for_reconnect => '900',
> general_inuse_check => '300',
> server_inuse_check => '900',
> cluster_inuse_check => '900',
> general_end_notice_first => '600',
> general_end_notice_second => '300',
> ignore_connections_gte => '1440'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
