Try setting the linkCapacity attribute of the listener. It is by default
set to 250.
The linkCapacity is the number of messages that can be in-flight
concurrently for each link.
Thanks.
On Thu, Aug 10, 2017 at 5:59 PM, Dan Langford wrote:
> thank you. as i configure this Messaging service i am
thank you. as i configure this Messaging service i am now for fully
understanding why Azure Service Bus and RabbitMQ do not support
Transactions and Message Selectors :-)
Question about prefetch/acquired messages: i am finding that QDR will leave
some (up to 250 quite frequently) messages as acqui
On 09/08/17 16:59, Dan Langford wrote:
back from vacation now. i upgraded to 0.8.0 and local/session transactions
look like they are working as expected.
*Question about JMS filters / message selectors*: when i connect to my
artemis broker with the artemis client JMS filters work. when i connect
back from vacation now. i upgraded to 0.8.0 and local/session transactions
look like they are working as expected.
*Question about JMS filters / message selectors*: when i connect to my
artemis broker with the artemis client JMS filters work. when i connect to
my artemis broker with qpid-jms-clien
Thank you all very much. i will upgrade to dispatch router 0.8.0 and forget
about XA transactions. i was thinking that all of these brokers out there
support XA transactions and i am now realizing that they support XA on
protocols that are not AMQP 1.0. in the past few days i have also studied
more
On 1 August 2017 at 22:20, Dan Langford wrote:
> ( github gist with all the config and data from the Original Post
> https://gist.github.com/danlangford/4944dcc6c0d2703ffb8555603ed27340 )
>
> YES i was under pretty light load. a couple hundred or thousand messages at
> a time were all getting funn
On 01/08/17 22:20, Dan Langford wrote:
are transactions expected to work with qpid dispatch router?
The router itself does not support transactions (it does not do any
storage of messages). From 0.8 you should be able to link route (local)
transaction requests to a transaction coordinator suc
( github gist with all the config and data from the Original Post
https://gist.github.com/danlangford/4944dcc6c0d2703ffb8555603ed27340 )
YES i was under pretty light load. a couple hundred or thousand messages at
a time were all getting funneled into the local broker. You are right once
i got 7 or
Dan,
There's one issue with your configuration which doesn't affect the load
balancing but will cause problems with receiving messages from the
brokers. In the address.prefix, you use "foo.#". This is a pure prefix
and it should simply be "foo". The wildcards are coming in the next
release but
