qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Giusti <kgiu...@redhat.com>
Subject Re: Maybe bug, maybe novice mistake, or maybe my python qpid library is too old.
Date Wed, 10 Apr 2013 14:56:01 GMT
Good catch Bill - this is a bug, and I've entered a JIRA for it:


That said, I would urge you not to use the QPID connection directly.  The API doesn't explicitly
expose this, and we probably will be moving the QMF client to use the client messaging interface
at some point (which will break what you're doing).

Instead, you should create a separate connection to the broker using the "Qpid Messaging client
API" as described here:



----- Original Message -----
> From: "Bill Freeman" <ke1g.nh@gmail.com>
> To: "users" <users@qpid.apache.org>
> Sent: Tuesday, April 9, 2013 5:56:34 PM
> Subject: Maybe bug, maybe novice mistake, or maybe my python qpid library is too old.
> In my qmf.console based app, I was trying to figure out how to piggy-back
> my browsing of a queue
>  on the existing broker's connection, using
> broker.conn.session('somename'), and while pdb was trying to print a stack
> trace, the __str__ method of the qpid.connection.Connection instance got
> called.  This does (at line 225 in my copy):
>     return "%s:%s" % self.sock.getsockname()
> Now,  getsockname() returns:
>     ('::1', 49845, 0, 0)
> So it's no wonder that pdb gets a:
>     TypeError: not all arguments converted during string formatting
> I'm guessing that the code was written before getsockname() became IPv6
> aware?
> Bill


To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message