Closed akhenry closed 9 months ago
@akhenry I think I'm reproducing the issue and I've got a PR with a script and an example XTCE. Here's a sample parameter that I've fed ~2.6MB worth of image data to with the default writeBufferWaterMark
:
Note the value is missing, and attempting to go to Historical Data either causes Chrome to "Ah, Snap" or just shows blank values.
Here's with writeBufferWaterMark
set to 160000000
:
Note the value is visible, and you can go to Historical Data, wait, and see values.
Summary
Impacts both Open MCT and Yamcs. Initially we need a minimal reproduction in Yamcs-Quickstart using the default high water mark there.
Yamcs will drop a socket if the buffer fills up and is no longer writable. This appears to be due to a potential impedance mismatch between the buffer used to store the serialized message, and the buffer used to write out to the WebSocket.
The prevailing theory is that this occurs when a serialized message is larger than the high water mark of the write buffer.
Issue is being recorded here first so that we can provide a minimal reproduction of the issue using Yamcs Quickstart with the default settings for high and low water marks -
setParameterValue
.