Bug 55258 – Add description for umc/http/response-timeout

Bug 55258 - Add description for umc/http/response-timeout


Summary:	Add description for umc/http/response-timeout

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UCR
Version:	UCS 5.0
Hardware:	All All

Importance:	P5 minor (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-10-12 12:47 CEST by Thorsten
Modified:	2022-10-12 12:47 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Thorsten

2022-10-12 12:47:55 CEST

`ucr search` does not provide any insight on the variable `umc/http/response-timeout`. Please add some description/documentation.

I asked the following questions on that variable internally:

- Is 310 as default not a little high for a timeout that most likely will occur on synchronous user interaction?
- Why is the value that's used in the configuration the value I set in UCR but +1?

And got the following answer that might be a good starting point:

"we have some long-polling HTTP requests, where we wait for some operations to finish. They can sometimes take several minutes.

The default value is plus one second to fix a race condition. The timeout is not only applied by apache but also internally be the UMC-(Web?)-Server: if that times out it responses with a more accurate error than apache which just breaks up the connection. So we give the UMC-Server that time to respond earlier."