Hi all,
I just pushed my initial adaptation of Python's qpidtoollibs to Ruby. If you're
not familiar with it, qpidtoollibs is a set of classes used by the command line
tools (qpid-stat, qpid-config) to talk to the broker via QMF2 to query for
information and to create/delete exchanges, queues,
On Mar 1, 2013, at 9:24 AM, Aleš Trček wrote:
Ooops, my first posting, and I have already made a fool of myself... :)
Yes, the priorities work fine, I thought that lower numbers are higher
priorities when actually it is the opposite... That and not checking properly
the output I got.
So,
Please see
http://mail-archives.apache.org/mod_mbox/qpid-users/201112.mbox/%3c4ed91581@redhat.com%3e.
It's possible there was a bug in the past that resulted in multiple values for
the same key being displayed. But Gordon's answer makes sense, from an
implementation perspective - a key in
I'm not familiar with libqpid-ruby1.8, but if that's roughly equivalent to the
qpid_messaging rubygem, you can write Ruby code that sends QMF messages to the
broker to perform the actions you desire. There is a Python class that performs
these actions, and it is pretty easy to port over to Ruby
Hi Bruno,
You can try to look up an existing sender and reuse it if it exists. I just ran
a test and it significantly decreases the amount of time it takes to send a
large number of messages to the same queue. Something along the lines of this:
Sender tx;
bool create = false;
try {
On Jan 11, 2013, at 10:15 AM, Fraser Adams wrote:
On 11/01/13 13:11, Lance D. wrote:
Wow. Thanks for the huge amount of detail!
No worries, hope it helps. One of the best things about Qpid is the strong
user community, I've got a lot out of it so it's nice to be able to give a
little
Yes, they do convert the map or list to binary. The AMQP specification defines
the encoding at the wire level for all the various supported data types such as
maps, lists, fixed-width fields such as numbers and strings, and so on.
Andy
On Oct 22, 2012, at 10:15 AM, Joe Ly wrote:
Hi all,
Hi Joe,
You have a couple of tried true options. You could manually copy the data
from the struct into a Variant::Map and encode that into a Message. You could
use a library such as Google Protocol Buffers to both store the data in memory
(i.e. instead of using a struct you'd use a protobuf
Could you just take your class's properties and place them in a map?
Andy
On Oct 16, 2012, at 12:29 PM, Rajesh Khan wrote:
While studying QPIDD I realized that I could send maps and lists to
receivers like this
qpid::types::Variant::Map content;
content[id] =
On Tue, Oct 16, 2012 at 10:44 AM, Andy Goldstein
andy.goldst...@redhat.comwrote:
Could you just take your class's properties and place them in a map?
Andy
On Oct 16, 2012, at 12:29 PM, Rajesh Khan wrote:
While studying QPIDD I realized that I could send maps and lists to
receivers like
to route add, queue add, or dynamic add.?
Are there any usecases to invoke qpid-route link XXX without any subsequent
calls to route add, queue add, or dynamic add.?
Best Regards,
Sergey
-Original Message-
From: Andy Goldstein [mailto:andy.goldst...@redhat.com]
Sent: Tuesday, August
The add command establishes a connection between 2 brokers. This is required
in order for federation to work, and is done implicitly if you don't already
have a link when you run route add, queue add, or dynamic add.
The del command removes a connection between 2 brokers.
The list command
My vote is for (a)
Andy
On Aug 7, 2012, at 2:11 PM, Gordon Sim wrote:
So, to follow up and summarise this thread so far, the only contentious point
has been the loss of the 'flow to disk' functionality.
Though the current solution doesn't limit the memory used by a large queue,
it can
Are you building qpid from source? I usually use it as part of Red Hat's MRG
Messaging product, but you can also build it yourself from source. The source
code for the store is located at
http://anonsvn.jboss.org/repos/rhmessaging/store/. You'll probably need to get
the svn revision that
You can install boost via e.g. Homebrew, but once you get all the prerequisites
installed, you won't be able to compile everything. The qpid codebase uses gcc
(ELF) thread local support, and OS X doesn't support those directives.
Andy
On Jul 19, 2012, at 1:06 PM, aparikh wrote:
Trying to
I have a kqueue-based poller that I worked on several months ago. The thread
local implementation I put together for OS X is a quick hack and definitely
needs to be redone. See https://github.com/ncdc/qpid/tree/mac.
Andy
On Jul 19, 2012, at 3:03 PM, Steve Huston wrote:
No, those are
Try this:
call 146 purge 2 {}
Andy
On Jul 12, 2012, at 12:25 PM, aparikh wrote:
The call command to purge messages from the qpid queue is returning below
error... I have made sure the queue id is correct and there are messages in
the queue..
Any help would be appreciated..
Versions:
Take a look at qpid-cpp-benchmark - this coordinates running qpid-send and
qpid-receive, which are both coded using the messaging api.
Andy
On Jul 10, 2012, at 3:58 PM, mburkhart wrote:
The qpid-perftest sample (qpid-0.16/cpp/src/tests/qpid-perftest.cpp) appears
to still be using the
, Andy Goldstein agold...@redhat.com wrote:
What sort of events are you looking for? The broker does send out QMF
events when certain things occur, such as when a queue is created.
Andy
On Feb 12, 2012, at 11:46 PM, sinduja.rama...@gmail.com wrote:
Hi anyone,
Can anyone tell me
What sort of events are you looking for? The broker does send out QMF events
when certain things occur, such as when a queue is created.
Andy
On Feb 12, 2012, at 11:46 PM, sinduja.rama...@gmail.com wrote:
Hi anyone,
Can anyone tell me , is there any function or group of functions exists
The qpid::client API is an older API that is more closely tied to the
inner-workings of the AMQP 0-10 protocol.
The qpid::messaging API is newer and is generally recommended as the API to use
for new development effort. It is designed to abstract away from
protocol-specific details. This
Trina,
What version of the broker are you running? You may be running into a bug -
https://issues.apache.org/jira/browse/QPID-3352 - that was recently fixed.
Andy
On Nov 29, 2011, at 1:05 PM, Wisler, Trina wrote:
Thanks for your prompt reply Gordon.
We already recreate the routes
Could you please describe what your test program is doing in more detail -
perhaps post some sample code? When you say you're losing messages, where is
the loss occurring? If you've received and acknowledged messages, and then your
app is killed/crashes, these messages will be lost - once a
Hi Fraser,
How many messages can the ring queue hold before it starts dropping old
messages to make room for new ones?
Andy
On Sep 23, 2011, at 5:21 AM, Fraser Adams wrote:
Hello all,
I was chatting to some colleagues yesterday who are trying to do some stress
testing and have noticed
happened a lot
sooner obviously.
Fraser
Andy Goldstein wrote:
Hi Fraser,
How many messages can the ring queue hold before it starts dropping old
messages to make room for new ones?
Andy
On Sep 23, 2011, at 5:21 AM, Fraser Adams wrote:
Hello all,
I was chatting to some
on a receiver.
Andy
Cheers,
Frase
Andy Goldstein wrote:
As an experiment, try lowering the # of worker threads for the broker. For
example, we saw an order of magnitude increase in performance when we
dropped worker threads from 8 to 2 (on a 48-core server). Our test involved
creating
I believe that exchange and dynamic routes automatically try to avoid loops
using trace IDs and excludes, but queue routes do not have this configured
automatically. You can specify arguments when you create your source queue
(qpid.trace.id and qpid.trace.exclude) to achieve similar behavior.
Hi all,
I've found a couple of 404s on the web site and wanted to report them. On
http://qpid.apache.org/documentation.html, all the links under API Reference
Documentation for 0.7 are broken. This includes both the HTML versions and the
.tar.gz versions.
Andy
28 matches
Mail list logo
