Hi,
I have some question for fanout queues.
Que1 - I have a fanout exchange and there are 2 queue's attached to the
fanout exchange. Now, when the messages are coming to the exchange, and
being replicated to both the queues. What will be the space occupied by
these messages, as they are the same
Hi Christopher,
What is the version of your broker?
In case if broker version >= 0.16, I found so far 2 scenarios leading
to these issue:
1) queue was created as exclusive, consumer subscribed, and
exclusivity flag was reset through JMX while consumer was still
present
2) queue was created as
The "target" capacity was meant for producer flow control which was
never implemented.
The "source" capacity is used as message credits for the subscription.
However flow control is controlled at the session level.
That is the unacked messages for the session is taken into account
when issuing com
Hi ,
I am using C++ Qpid Broker(MRG 0.14) and Java JMS client.
I understand from the QPID documentation and google resources that we can
set the consumer capacity which effectively works at session level rather
than consumer level in Java.
Please let me know what does the source and target mean in
Good morning. So far my qpid experience has been quite smooth, and using it has
been comparatively relaxing. Of course my hitch would come when I try to mash
up qpid, activemq, and camel. I'm asking my question here since I'm having a
problem with the mix, and the only inconsistency I can find s
So ran the below command
/configure --with-qpid-checkout=/opt/qpid_source/qpidc-0.16/
--with-qpid-buildr=/opt/qpidc-0.16
where
/opt/qpid_source/qpidc-0.16/ is the source (just tar xvf for for
qpid-cpp-0.16.tar)
/opt/qpidc-0.16 is where configure and make is done for qpid-cpp-0.16.tar
Received
Hi All,
I'm looking to set up a durable HA broker and had a few questions.
First off, sorry if these questions are more appropriate on a Linux-HA
forum... just trying to see if other people have come across the same
issues.
After setting up a two node cluster and being quite happy with the
ease o
Hi Gordon,
Thanks a lot
Best Regards,
Sergey
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Thursday, July 26, 2012 5:59 PM
To: users@qpid.apache.org
Subject: Re: Message Listeners/Subscribers with messaging API
On 07/26/2012 12:37 PM, Zhemzhitsky Sergey wrote:
> I
On 07/26/2012 12:37 PM, Zhemzhitsky Sergey wrote:
Is there any simple way to use something like message
listeners/subscribers with qpid messaging API except for using custom
threads which will continuously invoke Receiver.fetch(Message,
Duration)?
No, you need to do any dispatching to listeners
Hi there,
Is there any simple way to use something like message listeners/subscribers
with qpid messaging API except for using custom threads which will continuously
invoke Receiver.fetch(Message, Duration)?
Best Regards,
Sergey
___
The inf
Hi!Thanks for your Reply. Not only for testing network failure. I have a Qpid
Cluster of two nodes running well for many days.However,similar error is
reported as "critical Unexpected error: Timed out waiting for daemon" ,
messages as "eth0: link is not ready " found in system
log:/var/log/messag
Done - QPID-4168. Thanks!
-rob
p.s. - Apologies if the mailing list doesn't thread this correctly; my mail
client is acting a bit odd today (or I am just using it poorly).
Good detective work, Rob! Could you please open a jira for this issue?
Then we can track it, and if the decision is made
On 07/25/2012 10:00 PM, aparikh wrote:
qpidc-0.16 came from below url.
http://qpid.apache.org/download.html
Component downloaded is
C++ broker & client qpid-cpp-0.16.tar.gz [PGP]
That should be fine, just point --with-qpid-checkout to the directory
you extracted the source to, and point --wi
13 matches
Mail list logo
