[
https://issues.apache.org/jira/browse/VCL-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth updated VCL-934:
---------------------------
Affects Version/s: 2.4.2
Priority: Minor (was: Major)
Description:
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.
Component/s: vcld (backend)
Summary: Warnings generated in vcld.log for server requests
because frontend isn't inserting 'initialconnecttimeout' computerloadlog entry
(was: Warnings generated in vcld.log for server requests because frontend isn't
inserting 'initialconnecttimeout)
> 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
>
> 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)
