My apologies,
I completely misread and misinterpreted the method description.
Somehow I missed *all the bindings*" in my reading :(
The bindingKey is optional here because, for example, for canonical
queue binding to fanout exchange the binding key is not needed.
Though, it is now possible to
is there way to configure the broker to treat TTL expired messages as other
"undeliverable" messages by delivering those to the configured Alternate
Binding?
On Tue, May 15, 2018 at 2:38 AM, Gordon Sim wrote:
> On 15/05/18 04:49, Mansour Al Akeel wrote:
>>
>> Gordon,
>> Thank you for replying. I am sorry I didn't explain it well. Maybe I was
>> relying on the link on ServiceMix mailing list. I will try to explain it
>> again here.
>>
Hi Alex,
I think the wording is at least ambiguous when you take into account the
fact that bindingKey is marked as optional; and that if you read it as
requiring an exact match of both destination and binding then the
wording "Deletes
*all the bindings*" is weird - because there can only be 0 or
Hi Olivier,
The current description of unbind operation on master and 7.0.x states
: Deletes all the bindings matching the given destination and
bindingKey
As per description the queue binding is deleted only when both
destination and binding key are equal to provided destination and
bindingKey
Hello,
According to the apidocs/latest/exchange documentation, it's possible to remove
all bindings for a given destination (here a queue) using the 'unbind'
operation.
But when testing it, it only works when specifying both the destination and the
bindingKey.
Is it something that should be
Hi folks,
I built a candidate release for version 6.3.1 of Qpid JMS AMQP 0-x.
Please test and vote accordingly.
The source and binary bundles can be taken from:
https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.1/
The maven artifacts are also staged at:
On 15/05/18 04:49, Mansour Al Akeel wrote:
Gordon,
Thank you for replying. I am sorry I didn't explain it well. Maybe I was
relying on the link on ServiceMix mailing list. I will try to explain it
again here.
We have two systems, on separate networks. System A and System B. Each of
them provide