[
https://issues.apache.org/jira/browse/VCL-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152595#comment-15152595
]
ASF subversion and git services commented on VCL-934:
-----------------------------------------------------
Commit 1731094 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1731094 ]
VCL-934
Added check in reserved.pm for server requests when retrieving
'initialconnecttimeout' computerloadlog entry to prevent warnings in vcld.log.
> Warnings generated in vcld.log for server requests because frontend isn't
> inserting 'initialconnecttimeout' computerloadlog entry
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: VCL-934
> URL: https://issues.apache.org/jira/browse/VCL-934
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Affects Versions: 2.4.2
> Reporter: Andy Kurth
> Priority: Minor
> Fix For: 2.5
>
>
> For server requests, the front end is populating reservation.remoteIP when
> the request is created. This causes the back end to essentially skip the
> stage where it waits for the user to acknowledge the request is ready -- they
> don't have to click the Connect button.
> The back end then immediately proceeds to the stage where it checks for a
> user connection. For normal reservations, the front end inserts a
> 'initialconnecttimeout' entry into the computerloadlog table when Connect is
> clicked. This isn't happening for server requests. As a result, the back
> end is generating warning messages in vcld.log for ever server request when
> it processes the _reserved_ state.
> This is benign but should be fixed. An easy way would be for the backend
> code could always insert an 'initialconnecttimeout' entry for server requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
