local-idle-timeout expired

Greetings, I observe following messages from qpidd in /var/log/messages: qpidd: 2017-11-29 13:11:47 [Network] error qpid.10.1.1.11:5672-10.1.1.1:65355 connection failed: transport error: amqp:resource-limit-exceeded, local-idle-timeout expired I assume these messages are generated when open

Re: Correct behavior for message delivery when receiver link is locally closed

+1 - Original Message - > From: "Alan Conway" > To: "Andrew Stitcher" , "Clifford Jansen" > , "Justin Ross" > , "Gordon Sim" , users@qpid.apache.org > Sent: Tuesday, November 28, 2017 2:34:28

Re: Correct behavior for message delivery when receiver link is locally closed

On 28/11/17 19:34, Alan Conway wrote: I noticed a discrepancy on how PN_DELIVERY is handled by different bindings 1. C++ - if (link is locally closed and auto_accept is set) { release the message } else { call on_message } 2. Python - if (link is locally closed) { if (auto_accept is set)

Correct behavior for message delivery when receiver link is locally closed

I noticed a discrepancy on how PN_DELIVERY is handled by different bindings 1. C++ - if (link is locally closed and auto_accept is set) { release the message } else { call on_message } 2. Python - if (link is locally closed) { if (auto_accept is set) release the message} else call on_message 3.

Re: QPID C++ Broker: Message Routing

On 28/11/17 16:52, andi welchlin wrote: I could do it without a key like: qpid-route route add localhost:9001 localhost:9002 ex '' But will this lead to defined behaviour? With a key given which is empty? For a topic exchange that will I think only match where the routing key is also an

Re: QPID C++ Broker: Message Routing

On 28/11/17 16:48, andi welchlin wrote: Thank you, Gordon. It works. Is it possible to set the route without any key? I do not need it but I had to give it a key, otherwise the qpid-route utility exits with usage output: You could try with '#' (which means everything on a topic exchange). (If

Re: QPID C++ Broker: Message Routing

I could do it without a key like: qpid-route route add localhost:9001 localhost:9002 ex '' But will this lead to defined behaviour? With a key given which is empty? On Tue, Nov 28, 2017 at 5:19 PM, andi welchlin wrote: > Hello, > > I tried to create a route between

Re: QPID C++ Broker: Message Routing

Thank you, Gordon. It works. Is it possible to set the route without any key? I do not need it but I had to give it a key, otherwise the qpid-route utility exits with usage output: - qpid-route route add localhost:9001 localhost:9002 ex Usage: qpid-route

Re: QPID C++ Broker: Message Routing

On 28/11/17 16:19, andi welchlin wrote: Hello, I tried to create a route between exchanges. When I sent a message to the exchange on the first broker I did not get the message when I tried to read from the second broker. What I did is simple: - Startet two qpid daemons one on port 9001 and

QPID C++ Broker: Message Routing

Hello, I tried to create a route between exchanges. When I sent a message to the exchange on the first broker I did not get the message when I tried to read from the second broker. What I did is simple: - Startet two qpid daemons one on port 9001 and one on port 9002. - qpid-config -b

Re: Publishing message into non-existing destination over anonymous relay within a transaction

Hi The broker and client behaviours are fully compliant with "Using the Anonymous Terminus for Message Routing" [1]. It conforms the requirements of section "2.2.2 Routing Errors". For the cases, when destination cannot be resolved {quote} If the source of the link supports the rejected outcome,