You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to cobble together a small service that runs a given network job, runs a liveview server during the run and keeps the log viewer open for later usage. I'm not using Xpresso as I'd like to keep this setup as lightweight as possible; the output of the log viewer works perfectly for my use-case.
The problem is the following: if a user keeps viewing this log, their browser keeps polling the server for updates, which creates short-lived TCP connections that go into a TIME_WAIT state. Should the user want to run a different test (or rerun the current test), they'd have to restart the pyats process (which my script does), but due to the existing TCP connections stuck in a TIME_WAIT state, the process is unable to bind to the socket due to this missing socket option.
This problem would be resolved if this socket option were added to the web server sockets spawned by the liveviewer/log viewer.
The text was updated successfully, but these errors were encountered:
Hey folks,
I've been trying to cobble together a small service that runs a given network job, runs a liveview server during the run and keeps the log viewer open for later usage. I'm not using Xpresso as I'd like to keep this setup as lightweight as possible; the output of the log viewer works perfectly for my use-case.
The problem is the following: if a user keeps viewing this log, their browser keeps polling the server for updates, which creates short-lived TCP connections that go into a TIME_WAIT state. Should the user want to run a different test (or rerun the current test), they'd have to restart the pyats process (which my script does), but due to the existing TCP connections stuck in a TIME_WAIT state, the process is unable to bind to the socket due to this missing socket option.
This problem would be resolved if this socket option were added to the web server sockets spawned by the liveviewer/log viewer.
The text was updated successfully, but these errors were encountered: