Red Hat Bugzilla – Bug 591320
qmfv2 default bindings are too generic
Last modified: 2011-08-12 12:04:40 EDT
Description of problem:
The default routing key bindings for qmfv2 are too generic, resulting in a great deal of needless message propagation.
Example: "agent.ind.data" - used for binding for agent events - will receive all events regardless of need or interest.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
FYI: these log messages are issued by the broker - indicating that the queues are filling up:
May 11 15:34:33 pman08 qpidd: 2010-05-11 15:34:33 error Execution exception: resource-limit-exceeded: Policy exceeded on
qmfc-v2-pman07.lab.bos.redhat.com.31942.1, policy: size: max=104857600, current=104839272; count: unlimited; type=reject (qpi
The following Python fragment illustrates how to limit the kind of updates that are received by a console:
from qmf.console import Session, DebugConsole
c = DebugConsole()
s = Session(c, rcvObjects=True, userBindings=True)
b = s.addBroker()
By selecting the userBindings option in the Session, the client app is indicating that it will use calls to bindPackage/bindClass to indicate which classes of object it wishes to hear about.
Fixed upstream at revision 943589.