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.

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

Heartbeats #3

Open
GoogleCodeExporter opened this issue Nov 2, 2015 · 5 comments
Open

Heartbeats #3

GoogleCodeExporter opened this issue Nov 2, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

It looks like the client is sending a the broker a heartbeat value, but,
being single threaded, I'm presuming that it's not maintaining actual
heartbeats.

What's the status of this feature? Should heartbeats always be 0?

As a side question, in the absence of heartbeats, what's a good/cheap way
to actively test the broker connection to confirm we can still talk to the
broker? E.g. as a hack (or maybe good design, shrug :) I'm declaring a
non-durable queue whose sole purpose is to let me communicate with the broker.

Original issue reported on code.google.com by g%[email protected] on 1 Sep 2009 at 1:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant