Bug 624798 - QMF Ruby bindings need ConsoleSettings support for bind_package/event/class to work.
Summary: QMF Ruby bindings need ConsoleSettings support for bind_package/event/class t...
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf
Version: beta
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Ted Ross
QA Contact: MRG Quality Engineering
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-17 19:43 UTC by Ken Giusti
Modified: 2018-10-30 17:28 UTC (History)
4 users (show)

Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Ken Giusti 2010-08-17 19:43:27 UTC
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:
Actual results:

Expected results:

Additional info:

Comment 1 Pete MacKinnon 2010-08-17 19:52:21 UTC
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)


store = console.object(:class=>"Store")

Note You need to log in before you can comment on or make changes to this bug.