B4J Question Websocket crash in release mode

I discovered Jserver is buggy with UI apps. So I had to split the program apart into two halves. the server half, and UI half. Kludgy in my opinion but I guess it is what it is.

techknight said:

I discovered Jserver is buggy with UI apps

Click to expand...

You should read the documentation. jServer can only be used in non-ui projects.

And I dont understand why that is. Java is Java?

Same here,
I only noticed this after my program was finished and I started the program in release mode
But with another error:

A normal Webserver Handler works for my REST API, btw

Unfortunately, this documentationdoesn't say anything about
https://www.b4x.com/b4j/help/jserver.html#server
Also the Websocket Tutorial says nothing about it.
Only in the web server tutorial i found one line:
"A server program is a non-UI program."

But no matter, because I want to stream my Form to a website, I have to run a second non-GUI application at the same time. No Porblem for now i think.

But just out of interest I would also like to know why it works in debug mode but not in the release. How it works? I thought debug just compile some logging code into.
Couldn't there be a trick to simulate the server in debug mode?

The way ui projects handles threads is very different from which the jserver does. It works in debug mode because in debug everything incluiding the ui runs on the same thread. That is something you don't want on jserver.

So in order for this to ever work, we would need a jServerFX. I had a feeling something was up when the Create Websocket Class was missing from the list of options for the UI app.

Anyways, I ended up ditching Websockets in favor of MQTT because the problem with Websockets is lag time.

For example if I have 10 clients connected, and I am sending data through a For Each loop, it could be a second or two before it reaches the end, and anything that is timing related now gets blown out of the water.

I was not sure if it was even possible to "broadcast" to all clients at the same time on Websockets, so I went to MQTT.

That worked MUCH better and it is compatible with UI apps.

In my case I wasnt using any web pages. I was trying to connect multiple apps together at the server, at the same time. When the server clock ticks, all the clients tick at the beat of the server.