[Isomorphic]

Well, you saw the error log reporting the message as "too big," but yes that's odd if you're saying you don't have any large DSRequests. Are you using the Embedded Tomcat shipped with our SDK? If you're using your own it will probably still have the stock limits mentioned (8K or 16K) which might be small enough to break your use case.

Can you create a standalone repro case for us? Perhaps based on some of the samples included in the SDK? (smartclientSDK/examples)

[claudiobosticco]

Hello, I’m using my Tomcat server. I’d be interested in trying out the new configuration, as this could exclude or confirm a problem with my tomcat.
Could you let me know when the documentation will be available, please?

Regarding the standalone test case based on a showcase sample, I assume you mean that I have to run it on my Tomcat server, as I believe it would work in the SDKs, right?

Also, I wanted to ask: since remote debugging works for me with the older framework versions, would it be helpful to know when it stopped working, or not?

[Isomorphic]

We've simplified the way you provide websocket configuration. You can now just add it to WEB-INF/web-tomcat.xml, as described in the section on WebSocket Configuration here. It's already configured at 256K bytes if you use the Embedded Tomcat included in the SDK, but if you use your own, you'll need to ensure you add that configuration.

We also improved logging so that when a "too big" error is reported on the server, it also attempts to report the max message limits from the container. On the client, if you enable debug logging for category "messaging" it should report what message sizes are being sent (only for "large" messages - otherwise it would be a flood).

These fixes are available now, in the nightly builds of 13.1 dated 2024-09-29 and beyond and in the nightly builds of 13.0 dated 2024-09-30 and beyond.

[claudiobosticco]

SmartClient Version: SNAPSHOT_v13.1d_2024-09-29/Enterprise Deployment (built 2024-09-29)

I can confirm that without the WebSocket configuration I see this new WARN in the tomcat logs:

2024-09-30T22:01:29,410 [ ] WARN MessagingWebSocketEndpoint Websocket message size limits - max text: 8192, max binary: 8192

while with the new configuration added in the web.xml it's working, thank you very much!