You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Torquebox in a clustered environment Backstage does not include consumers running on others servers in the consumer count on the queues or topics pages.
Is this by design? Or is it a limitation of JBoss and HornetQ? If not then I think it would be valuable to add it.
The text was updated successfully, but these errors were encountered:
This is the nature of backstage and HQ - backstage just uses JMX to
discover those consumers, and JMX only shows consumers on the current
node. It would be nice to make backstage more cluster-aware, but that
may be a considerable amount of work. We'll have to talk/think about
that. Of course, if someone wanted to take that on and send a pull
request, no one would complain :)
Jeffrey Jones writes:
When running Torquebox in a clustered environment Backstage does not
include consumers running on others servers in the consumer count on
the queues or topics pages.
Is this by design? Or is it a limitation of JBoss and HornetQ? If not
then I think it would be valuable to add it.
Reply to this email directly or view it on GitHub: #22
Nuts, I was worried that might be the case, oh well. No chance of a pull request from me I am afraid so I will close this for the moment.
If something happens in the future where the situation changes I will resurrect this like a mad scientist with a storm-based electricity supply and a hunchbacked helper.
When running Torquebox in a clustered environment Backstage does not include consumers running on others servers in the consumer count on the queues or topics pages.
Is this by design? Or is it a limitation of JBoss and HornetQ? If not then I think it would be valuable to add it.
The text was updated successfully, but these errors were encountered: