I have been seeing some strange behavior with the 0.20 C++ broker (I see the
same behavior in the 0.14 broker as well) when sending / receiving messages
with the Python API. It seems that the response time increases for each
consecutive message.
The client sends a message with a reply-to
create one per response but never close them. Try adding
sender.close() after the send in the service program.
-Ted
On 04/24/2013 11:50 AM, Wes Parish wrote:
I have been seeing some strange behavior with the 0.20 C++ broker (I see the
same behavior in the 0.14 broker as well) when sending
Is it possible to connect to a pre-defined ring queue using JMS in browse mode?
If so, are there any examples?
Please correct me if I am wrong, but the way I uderstand it browse mode will
make a callback for every message on the queue when a user connects, then again
for each new incoming
Is it possible to set up a dynamic ring queue using JMS? This is with
MRG v1.2.
Wes
We have a broker with a modest amount of RAM, but a very large disk capacity.
Can we create a small in-memory queue, but a large associated journal (for
persistence)? Basically, we want to allow a persistent queue to hold a larger
number of elements than the broker has physical RAM to store
10:24 AM
To: users@qpid.apache.org
Subject: Re: Large persistent queues
On Thu, 2010-06-10 at 08:10 -0500, Wes Parish wrote:
We have a broker with a modest amount of RAM, but a very large disk capacity.
Can we create a small in-memory queue, but a large associated journal (for
persistence
the listener?
No, we do not get notified via the exception listener. We do see the
exception on stdout.
Rajith
On Wed, May 5, 2010 at 1:55 PM, Wes Parish w...@firstshotprecision.com wrote:
Rajith,
Thank you for the quick reply. We are running Red Hat MRG v1.2 official
release. Which version
When a connection exception is thrown because of a socket timeout exception,
which occurs when a heartbeat times out, it is not being sent to the
onException() method. Should this exception be sent like the others to this
method?
Wes
I have a question about the qpid::client::MessageReplayTracker C++ class. I am
using a MessageReplayTracker to send messages to a broker. Periodically when I
close the session and connection object from another thread I receive the
following warning message that is printed to stderr: Warning
I am not sure if Qpid natively supports being installed as a service, but if it
doesn't there is another option.
You can create a Windows service using SRVANY.exe from the Windows Server 2003
Resource Kit. Basically, you run the SRVANY.exe application and it installs
the service to your
Hello,
It seems like we are unable to pass the 30-40 MB/s rates (over a 1Gbit link)
using the Qpid. We have tried multiple configurations (current qpidd.conf
pasted below), but have not had any luck. Has anyone successfully seen
~100MB/s on a 1Gbit link?
Thanks,
Wes
I have seen similar problems (although no out of order messages so far). I am
testing on RHEL5.3 using the C++ API with a MessageReplayTracker to handle
failover, and after a failover I am calling replay().
This scenario is a consumer consuming as fast as possible, a producer producing
5k
the Buffer.
Best,
William
- Wes Parish wes.par...@cowtownt.org wrote:
Is the Qpid C++ Client API capable of transferring binary data? It
seems like the only data type in qpid/client/Message.h is the
std::string (data field of TransferContent.h).
I am interested in transferring segments
-Original Message-
From: Alan Conway [mailto:acon...@redhat.com]
Sent: Fri 5/22/2009 7:41 AM
To: users@qpid.apache.org
Subject: Re: Binary Data Transfer
Wes Parish wrote:
Is the Qpid C++ Client API capable of transferring binary data? It seems
like the only data type in qpid/client/Message.h
Is the Qpid C++ Client API capable of transferring binary data? It seems like
the only data type in qpid/client/Message.h is the std::string (data field of
TransferContent.h).
I am interested in transferring segments of binary data, and not ascii strings.
Is this possible with the current
Hello,
I would like to thank you guys for a great product, however, I am having a few
issues getting qpid setup correctly. I am able to bring up qpid fine on either
testbroker1 or testbroker2, but once a broker is running on one machine I am
unable to start qpid on the other. The error
16 matches
Mail list logo