Ted Ross wrote:
Gordon,
It looks from the patch that you have added special logic to suppress
the creation of the management objects related to "qpid-dump". I think
there's a cleaner way to do this without removing management visibility
into the qpid-dump objects.
If you grep for uses of "addObject" in the cpp/src/qpid/broker
directory, you will see that there is an optional second argument to
this method. It is used for persistent objects. Persistent IDs include
those held in the store and also IDs of default objects (i.e. the amq.*
exchanges).
You can use a "persistent" number space (like 0x400000000000XXXXLL) for
the qpid-dump objects. This will allow them to be managed but will
prevent them from skewing the allocation of non-persistent IDs.
Excellent suggestion, Ted! I will have a crack at that now. Thanks!
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]