Re: Java Broker performance

The test is sending persistent messages so the broker is obliged to write them to disk. After the arrival of each message transfer, the Broker-J awaits the sync'd to disk (after the write) before sending the Disposition performative back to the client. The Qpid JMS Client is awaiting the

Re: Electron/Amqp MessageAnnotations in Golang

On Fri, Nov 10, 2017 at 8:28 AM, Jiri Danek < jda...@redhat.com > wrote: > On Fri, Nov 10, 2017 at 1:10 PM, Alessio Gottardo > > wrote: > > > > Out of curiosity is there a specific reason for `panic`ing in the > > `default` case instead of returning an `error`?I just

Re: ACL rules for Qpid C++ Broker

Hi Andi, The ACLs for Qpid C++ are modeled after the AMQP 0-10 exchange-binding-queue (EBQ) design. See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/1.1/html/Messaging_User_Guide/sect-Messaging_User_Guide-Introduction_to_RHM-The_AMQP_0_10_Model.html for pictures and

Re: ACL rules for Qpid C++ Broker

Hello Jacub, this helps a lot. Thank you! Andreas On Fri, Nov 10, 2017 at 4:59 PM, Jakub Scholz wrote: > Hi Andreas, > > The problem is that in qpidd you never publish directly to queue or read > directly from an exchange. You always publish to exchange and read from a >

Re: ACL rules for Qpid C++ Broker

Hi Andreas, The problem is that in qpidd you never publish directly to queue or read directly from an exchange. You always publish to exchange and read from a queue. In reality what you see as publishing directly to an queue is sending the message to an exchange named "" (as in empty string) with

Re: Java Broker performance

On 10 November 2017 at 16:39, Vavricka wrote: > Hi, > > hardware: > * Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz > * 16 GB RAM > * HDD ST500DM002-1BD142 > > timings: > Currently Java Broker 6.1.1 seems to behave as version 7.0.0 RC. 10 - 30 > messages per second.

Re: Java Broker performance

Hi, hardware: * Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz * 16 GB RAM * HDD ST500DM002-1BD142 timings: Currently Java Broker 6.1.1 seems to behave as version 7.0.0 RC. 10 - 30 messages per second. Interesting is when I increase message size to 10kB. Messages per second are same but throughput is

ACL rules for Qpid C++ Broker

Hello everyone, I looked into ACL documentation of Qpid C++ broker (1.36.0) and tested it a bit. I would like to allow for one usergroup to write to a queue with a specific name, but deny it for all other users. But I saw that i can not do the following: acl allow group1 publish queue

Re: Java Broker performance

Hi Tomas, I'm testing with out of the box configuration. I have tried your configuration and still can't reproduce a slow down. I don't know your ACL rules, but I added some. The result was the same. I'm curious to hear the answers to the questions I posed earlier. Hopefully that will give us

Re: Java Broker performance

Hi Tomas, Nor can I reproduce any discernible difference in performance between 6.1.1 and the 7.0.0 RC with your Java code. I have not tried the C++ yet. Can you share with us: * details of the hardware (including the storage) you are using for the test. * the timings you seeing for your tests

Re: Electron/Amqp MessageAnnotations in Golang

On Fri, Nov 10, 2017 at 1:10 PM, Alessio Gottardo wrote: > > Out of curiosity is there a specific reason for `panic`ing in the > `default` case instead of returning an `error`?I just became aware of this > `recover` mechanism in go to handle a runtime `panic` thrown

Re: Java Broker performance

Yes, we running it on same hardware and versions. Couldn't be there issue with our configuration? Can you spot there some misconfiguration in config files below? Will be helpful if you send us your broker configuration? config.json { "id" : "cfa9a57a-6f98-4f17-b81d-22fb5a032473", "name" :

Re: SASL can not parse configuration file

Hello Gordon, hello all, now I got what is wrong with my SASL config. I mixed up qpidd.conf for the broker and qpidd.conf for sasl. These are two different files with the same name, right? So qpidd.conf for sasl should be similar to the file contained in "qpid-cpp-1.36.0/etc/sasl2". It could

Re: Electron/Amqp MessageAnnotations in Golang

Thank you Alan, very much appreciated :) Out of curiosity is there a specific reason for `panic`ing in the `default` case instead of returning an `error`?I just became aware of this `recover` mechanism in go to handle a runtime `panic` thrown somewhere else, but that's going to make the code

Re: SASL can not parse configuration file

Hi Gordon, It contains two files: qpidd.conf qpidd.sasldb On Fri, Nov 10, 2017 at 12:05 PM, Gordon Sim wrote: > On 10/11/17 10:31, andi welchlin wrote: > >> Hello all, >> >> I tried to configure SASL for Qpid C++ broker 1.36.0 but it seems like I >> missed something. >>

Re: [VOTE] Release Qpid Broker-J 7.0.0 (RC3)

On 8 November 2017 at 17:35, Oleksandr Rudyy wrote: > HI all, > > Apache Qpid Broker-J 7.0.0 RC3 is built and ready for testing. > The following issues have been resolved since RC2: > > * QPID-8020 - [Broker-J] Rename binary and source distribution bundles for > broker-j > *

Re: Java Broker performance

Hi Tomas, on the producing side I cannot reproduce this difference on my laptop (MacBook Pro, running OS X), and I'm unaware of any changes that were made to the broker that would cause such a significant slowdown (I haven't looked at consuming yet). I presume you are running these tests on the

SASL can not parse configuration file

Hello all, I tried to configure SASL for Qpid C++ broker 1.36.0 but it seems like I missed something. What I did: Installed Cyrus SASL. Created a SASL database with a user "bob" using: saslpasswd2 -f qpidd.sasldb -u QPID bob Checked the db using sasldblistusers2 and it

Re: HA Cluster using Qpid C++ Broker 1.36.0

Hello Alan, thank you for your answer. I could install pacemaker using "apt-get install pacemaker". If you could give me some hints what to do to get it run it would be welcome. Thanks, Andreas On Wed, Nov 8, 2017 at 8:01 PM, Alan Conway wrote: > rgmanager has been

Re: Java Broker performance

Thanks Tomas, we'll look into this -- Rob On 10 November 2017 at 09:59, Vavricka wrote: > C++ client code below > > #include > #include > > #include > #include > #include > #include > #include > #include > #include > #include > #include > > class

Re: Java Broker performance

C++ client code below #include #include #include #include #include #include #include #include #include #include #include class Broadcaster : public proton::messaging_handler { private: std::string _account; std::string _password; std::string _host;

Re: Java Broker performance

Hi, when consumer is not attached sending of messages is slow too. We were running performance tests for Java Broker 6.1.1 before 6 months and there were no issues (throughput for 1K messages was around 10MB/s). rgodfrey wrote > Hi Tomas, > > are you saying that there is a significant