Message bus is no longer functioning correctly

Support
1

I’m seeing this message show up in the logs after a recent update

Global messages on 379645 timed out, message bus is no longer functioning correctly

Backtrace

message_bus-4.2.0/lib/message_bus.rb:748:in `block in new_subscriber_thread'
message_bus-4.2.0/lib/message_bus/timer_thread.rb:117:in `do_work'
message_bus-4.2.0/lib/message_bus/timer_thread.rb:95:in `block (2 levels) in queue'

What does it mean?

Version
2.9.0.beta8
(d5dc4ca0e9)

2

I am having same warning. With a big global_id

Global messages on 3244473 timed out, message bus is no longer functioning correctly

I am using

gem 'message_bus', '~> 4.4.1'

I also recently had issues with the long polling with streaming that’s when I noticed this warning.

Is it normal to have global message id this big ? It never resets ?

3

PR opened fix: subscriber thread never self heals after half open tcp connection by Mubramaj · Pull Request #388 · discourse/message_bus · GitHub

4

Issue has been addressed and merged on version 5.0.0 of message bus: