Re: [Broker-J] REST-API: how to determine consumer for acquired messages

Yes, I think that would solve the issue. With that ID I can then co-relate with the consumer objects returned by the getConsumers REST API. I see that the bug was moved to 8.0.0 release. It seems like a minor change though. Any chance it can be merged into the next dot release? Thanks, Timo

Re: Restrict TLS Versions and Ciphers using qpid proton-cpp API

I also took a look, and I don't think we have accessors for these in C++. I raised a ticket for it: https://issues.apache.org/jira/browse/PROTON-2139 On Thu, Oct 24, 2019 at 7:21 AM Gordon Sim wrote: > On 18/10/2019 3:11 pm, bajanfella wrote: > > I see that there is a pn_ssl_domain_set_protoc

Re: [Qpid-proton-cpp] Performance regression found in 0.29.0

Hi, Jira issue created: PROTON-2137 . Best regards, Rabih On Wed, Nov 20, 2019 at 5:01 PM Andrew Stitcher wrote: > Please raise a JIRA with all this information and the reproducer - it > is very hard to track fixes without this. > > Also you c

Re: [Qpid-proton-cpp] Performance regression found in 0.29.0

Please raise a JIRA with all this information and the reproducer - it is very hard to track fixes without this. Also you could attach your patch, but it is easier in this case to use a github PR with a reference to the JIRA. The Apache automation will tie them together and this makes it again easi

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

Hi Alex, Yes, currently there's no rush on my side, as I've found some workaround for the tests. Thanks, pon., 18 lis 2019 o 15:16 Oleksandr Rudyy napisał(a): > Rob, > > I do not have any tentative date for the release yet. > Potentially, the changes can be ported into 7.1.6 and released as p

Re: [Qpid-proton-cpp] Performance regression found in 0.29.0

Hello again, Here is a patch that we propose. All unit tests are green on the master. Can you please @Andrew Stitcher check if this patch is aligned with what you meant to do in (PROTON-2075) ? Best regards, Rabih & Ali On Tue, Nov 19, 2019 at 7:04 PM HADI Ali wrote: > Hello, > > After analys

Re: [Broker-J] REST-API: how to determine consumer for acquired messages

So I've pushed a change that will return the consumerId of the acquiring consumer - so for an acquired message you'd additionally something like: "deliveredToConsumerId" : "406c1d71-1189-41bf-a945-6d21f5fd0753" Does that meet your requirements? Thanks, Rob On Wed, 6 Nov 2019 at 01:54, Timo Naro

RE: Dispatch-Router statistics and CPU consumption

Hello Ganesh, In order to monitor our messaging cluster we're are fetching a few statistics every minute on both the brokers and the dispatch-routers. Today we are missing the CPU consumption and indeed I can't access the machine running the dispatch-router directly, I just have access to the AM