Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] After upgrade to v2.0 WS client settings missing "maxMessages" param #175

Closed
dmytro-landiak opened this issue Nov 8, 2024 · 0 comments
Closed

[Bug] After upgrade to v2.0 WS client settings missing "maxMessages" param #175

dmytro-landiak opened this issue Nov 8, 2024 · 0 comments
Assignees
@dmytro-landiak
Labels
Bug Something isn't working
Milestone
2.0.1

Comments

@dmytro-landiak
Copy link
Contributor

Describe the bug

After updating TBMQ to version 2.0.0, I encountered the following issue:

image

I can resolve it by configuring the setting through the UI. However, until this setting is applied, the WebSocket client page does not limit the number of messages stored in the browser’s memory per client.
@dmytro-landiak dmytro-landiak added the Bug Something isn't working label Nov 8, 2024
@dmytro-landiak dmytro-landiak added this to the 2.0.1 milestone Nov 8, 2024
@dmytro-landiak dmytro-landiak self-assigned this Nov 8, 2024
@dmytro-landiak dmytro-landiak mentioned this issue Nov 8, 2024
Merged
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmytro-landiak dmytro-landiak

Labels
Bug Something isn't working
Projects
None yet
Milestone
2.0.1
Development

No branches or pull requests
1 participant
@dmytro-landiak