Re: modified outcome with undeliverable-here

On Tue, Jun 21, 2016 at 4:54 PM, Justin Ross wrote: > On Tue, Jun 21, 2016 at 1:21 PM, Matt Broadstone > wrote: > > > Thanks for the quick response, and glad to hear I wasn't crazy after all! > > We had previously discussed the timeline for qpidd's

Re: modified outcome with undeliverable-here

On Tue, Jun 21, 2016 at 1:21 PM, Matt Broadstone wrote: > Thanks for the quick response, and glad to hear I wasn't crazy after all! > We had previously discussed the timeline for qpidd's 0.35 release a few > months ago on the list here, and at the time it was pending a

Re: modified outcome with undeliverable-here

On Tue, Jun 21, 2016 at 4:21 PM, Matt Broadstone wrote: > On Tue, Jun 21, 2016 at 4:16 PM, Gordon Sim wrote: > >> On 21/06/16 21:10, Matt Broadstone wrote: >> >>> Hi all, >>> >>> I have a test case I've set up as follows: >>> * receiver link created, and

Re: modified outcome with undeliverable-here

On Tue, Jun 21, 2016 at 4:16 PM, Gordon Sim wrote: > On 21/06/16 21:10, Matt Broadstone wrote: > >> Hi all, >> >> I have a test case I've set up as follows: >> * receiver link created, and attached to a durable queue on a qpid broker >> (v0.34) >> * sender link also attached,

Re: modified outcome with undeliverable-here

On 21/06/16 21:10, Matt Broadstone wrote: Hi all, I have a test case I've set up as follows: * receiver link created, and attached to a durable queue on a qpid broker (v0.34) * sender link also attached, which sends a string message "testing" * the receiver is set up to only receive one

modified outcome with undeliverable-here

Hi all, I have a test case I've set up as follows: * receiver link created, and attached to a durable queue on a qpid broker (v0.34) * sender link also attached, which sends a string message "testing" * the receiver is set up to only receive one message at a time (1 credit), and to renew

Re: Dispatch Max Connections

DuhŠ thanks Ted :( On 6/21/16, 7:17 AM, "Ted Ross" wrote: >On my system, "ulimit -n" shows a limit of 1024 open files (FDs). You > - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, June 21, 2016 5:33:36 AM > Subject: RE: [Qpid-dispatch] Duplication between sslProfile and connector > options > > Thank you Ganesh, > > I actually got it working using

Re: Dispatch Max Connections

On 06/21/2016 03:45 AM, Gibson, Jack wrote: Any tested the limits of the dispatch router's number of connections? I've created a pretty simple (rudimentary) test where I increase the number of consumer/producer processes. Each process either consumes or produces leveraging the proton

RE: [Qpid-dispatch] Duplication between sslProfile and connector options

Thank you Ganesh, I actually got it working using self-signed certificate and the "--ssl-certificate" and the "--ssl-key" params for qdmanage. Do you think using "--ssl-trustfile" is better security wise? One more question, do I have to use the same certificate between Consumer/Producers -->

RE: Qpid Proton Binaries

Hello David, At first, I searched also for Proton binaries but only found sites proposing very old versions of Proton. It also depends on the compilers you use and the flags which you need to support in your build. We have built Proton on Linux, Windows and Solaris with the C++ bindings and

Dispatch Max Connections

Any tested the limits of the dispatch router's number of connections? I've created a pretty simple (rudimentary) test where I increase the number of consumer/producer processes. Each process either consumes or produces leveraging the proton python API. It seems to start through connection