[NETCONF-376] Can the timeout for HTTP response be configured? Created: 17/Mar/17  Updated: 13/Aug/19

Status: Confirmed
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 8015

 Description   

Recent longevity test case fails on ConnectionError [0] after time suspiciously close to 60 minutes. I think the HTTP server ODL uses has a default timeout, and it closes any TCP connections not transmitting data for 60 minutes. I have not found any place which would allow the timeout value to be configured.

For the longevity test in question, we can rework the call to be non-blocking, but configuring timeout would be easier for us.

[0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-1node-notifications-longevity-only-carbon/1/archives/log.html.gz#s1-t1-k2-k5

 Comments   
Comment by Vratko Polak [ 17/Mar/17 ]

Debugging has revealed this error on our Python (requests) client:
('Connection aborted.', error(104, 'Connection reset by peer'))

This maybe indicates that abortive [1] TCP connection release occurred.

[1] http://docs.oracle.com/javase/8/docs/technotes/guides/net/articles/connection_release.html

Generated at Wed Feb 07 20:14:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.