Red Hat Bugzilla – Bug 624798
QMF Ruby bindings need ConsoleSettings support for bind_package/event/class to work.
Last modified: 2013-02-24 20:34:30 EST
Description of problem: The ruby wrapper needs to allow the console constructor to accept a ConsoleSettings object. The ConsoleSettings object allows the "userBindings" flag(s) to be set - without it, the bind_XXX api's will not work. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I believe this leads the wallaby-agent to consume high CPU in step with its qpidd broker that is deluged with reconnects for backed-up queues. Essentially the Session created in wallaby-agent has no choice but deal with all the QMF events that flow from the broker backup. We need a means to likely disable events and heartbeats, or at least register interest in specific Event packages and/or classes. wallaby-agent QMF setup code... console = Qmf::Console.new settings = Qmf::ConnectionSettings.new settings.username = username if username settings.password = password if password settings.host = host settings.port = port connection = Qmf::Connection.new(settings) broker = console.add_connection(connection) broker.wait_for_stable store = console.object(:class=>"Store")