I'd prefer stability of names to consistency of names. Many firms or
projects no longer have the engineer who set up their happily working
dependencies. #2 is the more persuasive argument, but it is only a
recommendation.
Bill.
On Fri, Oct 31, 2014 at 11:21 AM, Darryl L. Pierce
wrote:
> In Fe
Perhaps not relevant, but I'm using a python client with a C++ broker with
the (QMF) heartbeat interval (configured in the broker) at ten seconds. I
had occasion to instrument the actual time between heartbeats, and while
usually very close to (but always longer than) ten seconds, I have seen odd
Note: the version of the python QMF client where I have seen this is rather
old. (0.20) It is even a patched version to make v2 QMF work at all. I
must presume that you're using a new enough version (as part of your new
enough qpid-too) to have the final version of those patches (see list
discus
I know that this is also true in the python qmf client (which is probably
what underlies gpid-tool.
It seems reasonable to me that if you ASK for both, that you receive
information once in each form, so long as the broker agent supports both.
Bill
On Sat, Apr 26, 2014 at 12:09 PM, Jakub Scholz
Gordon,
Thanks. I'm trying to get trace logging enabled and/or a tcpdump. The
latter is probably problematic since the system is carrying sensitive data.
Bill
On Wed, Apr 9, 2014 at 11:27 AM, Gordon Sim wrote:
> On 04/09/2014 04:12 PM, Bill Freeman wrote:
>
>> Let me
Freeman wrote:
> Gordon,
>
> Thanks. We'll go about gathering more information as you suggest. (I
> haven't been directly involved. I'm just the stuckee for all matter Qpid,
> or so it seems.)
>
> Bill
>
>
>
> On Wed, Apr 9, 2014 at 10:28 AM, Gord
Gordon,
Thanks. We'll go about gathering more information as you suggest. (I
haven't been directly involved. I'm just the stuckee for all matter Qpid,
or so it seems.)
Bill
On Wed, Apr 9, 2014 at 10:28 AM, Gordon Sim wrote:
> On 04/09/2014 03:13 PM, Bill Freeman wr
We run a three node cluster, fed by federation links from non-clustered
brokers on what we call workflow servers. All C++ brokers (0.18,
probably). As near to simultaneously as we can tell (log has 1 second
resolution) we are seeing the following error on three (probably all of
the) workflow serv
On Tue, Apr 1, 2014 at 5:22 PM, Gordon Sim wrote:
> On 04/01/2014 10:03 PM, Bill Freeman wrote:
>
>> I'm receiving messages using the python qpid.messaging API, and getting a
>> value for x-amqp-0-10.timestamp that is an instance of
>> qpid.datatypes.timestamp, a
I'm receiving messages using the python qpid.messaging API, and getting a
value for x-amqp-0-10.timestamp that is an instance of
qpid.datatypes.timestamp, and whose value, when coerced to a str (print) or
to a float, is apparently miliseconds since the Unix epoch.
Yet looking at the implementation
Gordon,
Thanks again. This has been a great help.
Bill
Gordon,
First, thank you so much for your response.
Some stuff elided:
On Thu, Mar 6, 2014 at 5:17 AM, Gordon Sim wrote:
> On 03/05/2014 09:55 PM, Bill Freeman wrote:
>
...
> even for durable queues where the message body may only exist in the file,
>> and contrary to som
I've a few concerns about my understanding of the real meaning of the
various limits on queue content.
First, let me apologize that my questions need to be interpreted in the
context of the 0.18 release (upgrades here happen slowly, if at all).
Please tell me where I've got it wrong below:
1. Li
e JMS client itself to use and an application using this
> will have no effect on what a producer will do with a message when sending
> it).
>
> Robbie
>
> On 10 February 2014 21:37, Bill Freeman wrote:
>
> > One part of our world uses JMS 1.1 to interact with C brokers (
One part of our world uses JMS 1.1 to interact with C brokers (0.14, I
think). We would like all messages sent this way to be durable. I can do
this fine in the python API, but the JMS folks here tell me that JMS has no
support for such a thing. They have tried specifying "Durable" and
"durable"
Background:
We need to run qpid.messaging code on a box (call it "control box") that
has only ssh connectivity to the box running the broker call it "broker
box").
Port forwarding using SSH does work, but the local port created can be
connected to by any process on the control box. This is a red
Frase,
I just happen to be fooling around in the corresponding code in the python
client (adding my own "tcp+ssh" to work over an existing paramiko link).
What I would interpret as "registration" (the filling in of
qpid.messaging.transports.TRANSPORTS) happens when
qpid.messaging.transports is imp
ocesses. Does the
> Connection object serialize fine when transferring via the pipe?
>
> -Original Message-
> From: Bill Freeman [mailto:ke1g...@gmail.com]
> Sent: Wednesday, August 07, 2013 5:51 PM
> To: users
> Subject: Re: Python Connections Hang from Subprocesses
>
>
By the way, I presume that you know that you can have multiple sessions on
one connection?
On Wed, Aug 7, 2013 at 5:49 PM, Bill Freeman wrote:
>
>
>
> On Wed, Aug 7, 2013 at 5:35 PM, Eagy, Taylor wrote:
>
>> What O/S are you running this on?
>>
>>
>>
> Can you, even when the subprocess is hung, run something like spout,
> drain, or qpid-config, e.g.;
>
> qpid-config queues
>
> from another console window on the same box?
>
>
>
> Yes, I can connect to the queue if I try to connect from another module
> (which runs a
onnection-class.html#_ewait>(self,
> predicate, timeout=None):
>
> 213 result = self._wait(lambda: self.error or predicate(), timeout<
> http://qpid.apache.org/releases/qpid-0.22/messaging-api/python/api/qpid.messaging.endpoints-pysrc.html#
> >)
> 214 self.check_e
Subprocesses (using the subprocess module, or even the older exec stuff, as
opposed to threads, or even forked clones) are relatively trouble free in
python (except maybe on Windows, whose process model has that Microsoft
difference). I've certainly made multiple connections to a broker from one
p
ll be in the next release (as well as trunk).
>
> - Original Message -
> > From: "Bill Freeman"
> > To: "users"
> > Sent: Thursday, July 25, 2013 4:28:50 PM
> > Subject: Re: Telling v1 events from v2 events using qmf.console python
> QMF l
that.
>
> Adding a isV2 attribute to the event sounds like a good approach. Let me
> know, I'd like to patch that into 0.24 and trunk so it will be available in
> future releases.
>
> -K
>
>
> - Original Message -
> > From: "Bill Freeman"
>
I've started working on detecting when a queue has been deleted. One
possibility is to track the queueDelete QMF events.
I noticed that I get 2 of each event (using an older qmf.console that has
been patched as recently discussed to allow v2 to happen at all). Using
pdb to crawl up the stack, I
Since I did make my tool work with v2, and I am currently discarding v1
messages (*), I think that this won't impact me.
(* I have to discard the v1 messages, since we are not, as previously
proposed, delivering the v2 messages to a separate Console (callback)
method. So I'm slightly less certain
On Thu, Jun 20, 2013 at 4:46 PM, Andrew Stitcher wrote:
> I actually thought this was uncontroversial because we've indicated it
> is a deprecated API for so long. Is there still actually anything that
> users can't do with the messaging API that can do with the client API?
>
> Depending on how yo
Are you, perchance, using python 3.x?
It looks like qpid-config is designed for python 2.x, when print was still
a statement (as opposed to a function).
On Tue, Jun 11, 2013 at 4:41 PM, Rajesh Khan wrote:
> Any chance I am missing something here?
>
>
> On Tue, Jun 11, 2013 at 3:24 PM, Rajesh
Just a few thoughts:
Since it appears to be the only asynchronous python QMF client, my own
project needs the qmf.console package to continue to work.
I presume that those tools, which Ken mentions as being based on QMFv2 now,
do not use this package.
Now that (the patched version of) it is actu
With respect to only the problem of attempting to make initial connection
to a broker and handling the case in which the OS that broker is running on
may be down:
Since you are on a *nix box, you will have the epoll or select system call
available to you. I believe that you can initiate your own
It may be worth trying forward slashes (solidus) inside of the key_store
and truststore arguments, e.g.:
amqp://guest:guest@
/development?brokerlist='tcp://localhost:15771?ssl='true'&key_store='C:/ssl/java_client_keystore.jks'&key_store_password='password'&trust_store='C:/ssl/java_client_truststor
On Wed, Apr 10, 2013 at 12:42 PM, Ken Giusti wrote:
>
> - Original Message -
> > From: "Bill Freeman"
> > To: "users"
> > Sent: Wednesday, April 10, 2013 11:23:04 AM
> > Subject: Re: Maybe bug, maybe novice mistake, or mayb
Ken,
On Wed, Apr 10, 2013 at 10:56 AM, Ken Giusti wrote:
> Good catch Bill - this is a bug, and I've entered a JIRA for it:
>
> https://issues.apache.org/jira/browse/QPID-4732
>
> That said, I would urge you not to use the QPID connection directly. The
> API doesn't explicitly expose this, and
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. T
On Fri, Apr 5, 2013 at 3:38 PM, Ken Giusti wrote:
> - Original Message -
> > From: "Bill Freeman"
>
> QMF V2 has been available for some time now, and we've cut all the project
> tools and libraries over to speaking it. If we start down the road to
On Fri, Apr 5, 2013 at 2:37 PM, Bill Freeman wrote:
> On Fri, Apr 5, 2013 at 2:09 PM, Ken Giusti wrote:
>
>> - Original Message -
>> > From: "Bill Freeman"
>> ...
>> >
>> > However, it would be nice to know how to get the consol
On Fri, Apr 5, 2013 at 2:09 PM, Ken Giusti wrote:
>
>
> - Original Message -
> > From: "Bill Freeman"
> ...
> >
> > However, it would be nice to know how to get the console to only
> subscribe
> > to the V2 queues. It's not clear
Ken,
Yes, with the patch in, I get callbacks to my qmf.console.Console sub-class
instance's callback methods for both V1 and V2 updates.
There are some differences in the plumbing:
V1 initial updates carry properties only. V2 initial updates carry
both properties and statistics. Both are s
Thanks.
I'm snowed under. I'll try the patch in a day or so.
Bill
On Wed, Apr 3, 2013 at 12:56 PM, Ken Giusti wrote:
>
>
> - Original Message -----
> > From: "Bill Freeman"
> > To: users@qpid.apache.org
> > Sent: Wednesday, April 3, 20
On Tue, Apr 2, 2013 at 5:22 PM, Ken Giusti wrote:
> When console.py connects to a broker (via addBroker), it will attempt to
> query for the existence of the qmf.default.direct and qmf.default.topic
> exchanges. If that query succeeds, the console marks that broker as being
> V2 capable, and use
Fraser
On Tue, Apr 2, 2013 at 1:48 PM, Fraser Adams
wrote:
>
> > I found this (https://cwiki.apache.org/qpid/qmfv2-project-page.html). I
> > probably didn't go here the first time around because the link to it on
> > https://cwiki.apache.org/qpid/qpid-management-framework.html says that
> it
>
On Tue, Apr 2, 2013 at 4:31 AM, Fraser Adams
wrote:
>
>
> On 1 Apr 2013, at 22:15, Bill Freeman wrote:
> >
> > I realize that the final numbers come out the same. But this is to be an
> > interactive tool, used by people who are panicking because some queue
>
Ken,
On Mon, Apr 1, 2013 at 5:58 PM, Ken Giusti wrote:
> > That sounds delux, since they would probably even survive moving a broker
> > from one server to another (with a different IP address.
>
> Whoa, moving a broker won't guarantee the fed-tag would be the same :(
>
> You see, the fed-tag i
Ken,
On Mon, Apr 1, 2013 at 4:31 PM, Ken Giusti wrote:
>
> 2) uniquely identifying objects across multiple brokers. Yes, Gordon's
> correct, object names are usually only guaranteed to be unique within a
> broker, not across them. Partitioning them by IP address + port could
> work, as would
Fraser,
Thanks again.
There are a few comments interspersed below, but no reply is required.
On Mon, Apr 1, 2013 at 3:48 PM, Fraser Adams
wrote:
>
>
> On 1 Apr 2013, at 19:56, Bill Freeman wrote:
>
> >
> >
> > I believe that I fall into the data push camp, even
Fraser,
See below, time permitting.
On Mon, Apr 1, 2013 at 2:12 PM, Fraser Adams
wrote:
> Firstly to say that I'm currently on holiday under a qpid curfew :-) so I
> can only sneak in a quick response at the moment, I'll try to give some
> proper answers to questions posed in this thread later o
On Mon, Apr 1, 2013 at 12:21 PM, Gordon Sim wrote:
> On 04/01/2013 05:06 PM, Bill Freeman wrote:
>
>> since I have a dog and pony show coming up shortly, do you
>> know how to get the existing qmf.console stuff to send my updates as V2
>> (session has rcvObjects True).
&g
Ken,
Please forgive me if I say "browser" anywhere in here. I mean "broker" but
"browser" seems to fall out of my fingers in the heat of typing.
On Mon, Apr 1, 2013 at 11:36 AM, Ken Giusti wrote:
> Hi Bill (and Gordon) - sorry about not chiming in a bit earlier with this.
>
> Bill - though yo
On Mon, Apr 1, 2013 at 10:32 AM, Gordon Sim wrote:
> On 04/01/2013 02:12 PM, Bill Freeman wrote:
>
>> On Mon, Apr 1, 2013 at 8:24 AM, Bill Freeman wrote:
>>
>>
>>>
>>>
>>> On Mon, Apr 1, 2013 at 5:03 AM, Gordon Sim wrote:
>>>
>>
On Mon, Apr 1, 2013 at 8:24 AM, Bill Freeman wrote:
>
>
>
> On Mon, Apr 1, 2013 at 5:03 AM, Gordon Sim wrote:
>
>> On 03/29/2013 04:35 PM, Bill Freeman wrote:That console API is a bit of a
>> mixture of QMFv1 and QMFv2. I think there is a getObjectId() method, and
On Mon, Apr 1, 2013 at 5:03 AM, Gordon Sim wrote:
> On 03/29/2013 04:35 PM, Bill Freeman wrote:That console API is a bit of a
> mixture of QMFv1 and QMFv2. I think there is a getObjectId() method, and
> you can then call asMap() on that to get the v2 form.
>
Thanks. I'll h
On Fri, Mar 29, 2013 at 9:29 AM, Gordon Sim wrote:
> On 03/28/2013 08:52 PM, Bill Freeman wrote:
>
>> So it occurs to me to ask whether the correspondence between named queue
>> and object id survives broker restarts?
>>
>
> I believe with QMFv2 and qpidd, the obj
---Part 2
On Tue, Mar 26, 2013 at 1:39 PM, Gordon Sim wrote:
> On 03/26/2013 04:12 PM, Bill Freeman wrote:
>
>> 4. If necessary, I'm thinking of disambiguating object IDs across browsers
>> by decorating (the string representing) the object ID with (a string
>>
Many thanks - Bill
On Tue, Mar 26, 2013 at 1:39 PM, Gordon Sim wrote:
> On 03/26/2013 04:12 PM, Bill Freeman wrote:
>
>> Qpid brokers speak AMQP on the wire. Excluding command line arguments,
>> config files, stuff in the data directory, and possibly *nix signals,
>> b
Please pardon me if my questions are all clearly answered in the
documentation. I've been reading for a while, and am still in doubt.
While I have done C++ and Java programming in the past, I have a lot more
experience in C, and I've mostly been a Python programmer of late. So also
please excuse
55 matches
Mail list logo
