Lux client connection error

[AndrewMusser]

Describe the bug

The jsonWebSocketServer FUB reports error 50004 when a Lux client first attempts to connect. The ErrorString reported is THAT$'s NOT POSSIBLE. The issue only appears intermittently, and appears to primarily occur after doing a clean, rebuild, followed by an offline install. Note that this has only been tested/seen in simulation.

When the issue first appears, the jsonWebSocketServer.ClientInfo[0].ClientPort is continually incrementing, which shows the the ws connections are getting closed or dropped, and being re-established.

To reproduce

Follow the LPM bootstrap guide here: https://loupeteam.github.io/LoupeDocs/tools/lpm/guides/bootstrapping-a-project-with-lpm.html

Expected behavior

The client should connect automatically when the HMI is started, and the ClientPort should keep a fixed value. There should be no error on the FUB.

Additional information

Happens with version 1.4.0 of OMJSON.

[Joshpolansky]

From the original troubleshooting it looked like there was a connection timeout that wasn't getting reset. after fixing that, what is the new behavior?

Also, is this a bug in OMJSON or the websocket library?

[AndrewMusser]

The connection timeout fix was incomplete, as the timer wasn't being called before its .IN was forced back to TRUE. Currently experimenting with rearranging the timer logic to see if it fixes it.

The issue appears to be coming from the jsonWebSocketServer.c file in OMJSON.

[Joshpolansky]

Is this solved now or is it still getting the error sometimes?

[sclaiborne]

It looks like it was mostly solved but will be fully fixed after #24