autoBatch doesn't work
See original GitHub issueIssue Description
I’m not sure I correctly understand what autoBatch
in JavaScript should do, but even when I set it to false
, CometD batches a bunch of subscription/publishing messages that I do before the handshake is complete into one big websocket message and sends them over. This causes the dreaded The decoded text message was too big for the output buffer and the endpoint does not support partial messages
error. Am I missing something and is there some way I could make CometD not do that? CometD version is 3.1.10.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Add autobatch as default in local YOLOv5 runs #7540 - GitHub
Add autobatch as default in local YOLOv5 runs #7540 ... does have a few limitations, mainly that it does not work with Multi-GPU...
Read more >Why isn't my Auto Batch Creation Working? - Viewpoint Help
There may be a few factors as to why your Auto Batch Creation isn't working the way you would like it to. Take...
Read more >AutoBatch™ Plug-in for Adobe Acrobat
How it works? The AutoBatch™ provides easy to use interface for creating batch files that does not require any type of programming or...
Read more >Servicestack 4.5.4 AutoBatch requests failed validation
We have run into an issue where if one request fails validation it stops running through the rest of the requests and returns...
Read more >Autobatch – Automatic batch run - Imatest
Running Autobatch · Select folder (all files) Select all files in a folder. (The Matlab uigetdir function does not show the individual files.)...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
remote.deliver(...)
will enqueue the message on the session, and will try to flush it. The flush may happen later (e.g. lazy channel) and possibly in another thread (e.g. waking up a suspended/meta/connect
), so the sender won’t know if the transport failed to write the messages.@sbordet - yes, thank you for the support!