B4J Question WebSocket client error

[DarkoT]

I need help.
In the B4J environment (desktop Windows), I created a WebSocket server and a WebSocket client application. If I compile the server in release mode, it works, and the client application also works when run from the B4J IDE (debug mode).
However, if I compile the client app in release mode and run it in the Windows environment, the system reports an error — on the server side, I get the following: onWebSocketError: null.
Does anyone have any idea what could be wrong? Alternatively, how can I catch the error in release mode (everything works fine in debug mode)?

Br, DaT

 

[teddybear]

Here it works, which version of jwebsocketclient are you using?

 

[DarkoT]

Here it works, which version of jwebsocketclient are you using?

version 1.13 (internal)

It's really strange situation... In debug mode - everthing works perfect's, after I create windows exe, system will not connect (on same machine) to ws.. Really have no idea what is wrong, I made research over all net...

 

[Chris2]

version 1.13 (internal)

Assuming that you're using Java 11+, try this later version of jWebsocketClient: https://www.b4x.com/android/forum/threads/jwebsocketclientv2.156357/post-963635
There was a Jetty incompatibility I think that led to intermittant WS connection issues.

Edit: Incidentally, I think if you're using the latest B4J version the internal jWebsocketClient version should be 2.00

 

[teddybear]

version 1.13 (internal)

It's really strange situation... In debug mode - everthing works perfect's, after I create windows exe, system will not connect (on same machine) to ws.. Really have no idea what is wrong, I made research over all net...

Now I got you what you mean release mode is , you mean that is build standalone package.
You need to add this PackagerProperty for standalone

#PackagerProperty: AdditionalModuleInfoString = uses org.eclipse.jetty.websocket.common.RemoteEndpointFactory;

 

[DarkoT]

Now I got you what you mean release mode is , you mean that is build standalone package.
You need to add this PackagerProperty for standalone

#PackagerProperty: AdditionalModuleInfoString = uses org.eclipse.jetty.websocket.common.RemoteEndpointFactory;

Thank you for your help... That's the solution... I added an extra line with #PackageProperty to the client, and now the system works... Thanks for the help and best regards to the whole community... You guys rock

 

[Chris2]

Note that if at some point you update to use jWebsocketClient V2.00 then you'll need to use different PackagerProperty settings, as detailed in @Erel's post I linked to above.