What is the alternative to get the qpid-tools?
http://www.ubuntuupdates.org/package/core/trusty/universe/base/qpid-tools
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Why-qpid-tools-is-deleted-in-trusty-tp7616688.html
Sent from the Apache Qpid users mailing list archive at
Any idea about this? It happens pretty random.
Program terminated with signal 6, Aborted.
#0 0x7f96804b1425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x7f96804b1425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f96804b4b8b in abort () from /lib/x86_64-lin
This probably does not matter. I think legacystore.so is the one that is
working.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Why-performance-of-sending-durable-messages-to-qpid-queue-is-really-bad-tp7609368p7609543.html
Sent from the Apache Qpid users mailing list archiv
Thanks for that. After changing it from 500 to 10, I am able to get 20ms
latency for a send. Pretty cool.
But I cannot reproduce it on another machine, i.e. after I copied the
rebuilt qpidd executable with reduced timeout to another machine, the
latency is still 1000ms on that machine, unless I re
I am not sending big messages, just a couple of words. Indeed, I use AMQP
1.0. Then it seems the static 1000ms latency comes from qpid timeout for
waiting more messages to write to the store. Can I adjust the timeout value
in qpid source code? I would be happy if we could reduce it to 100ms for
dur
I am not able to do that.
./qpidd --daemon --wcache-page-size 4 --config /etc/qpid/qpidd.conf
[Broker] critical Unexpected error: Error in command line options: ambiguous
option wcache-page-size
Use --help to see valid options
--
View this message in context:
http://qpid.2158936.n2.nabble.c
It is the qpid c++ broker. The BDB store is used. Is there a way to improve
the performance while preserving the persistence?
qpidd.conf
data-dir=/var/spool/qpid
mgmt-enable=yes
load-module=/usr/local/phonefactor/bin/legacystore.so
load-module=/usr/local/phonefactor/bin/qpid/store/store.so
>From
With Proton c++ client, it seems sending an undurable message to a qpid queue
takes 1-3ms, while sending a durable message takes static 1000ms. Is it by
design? Why does it take so much time?
My code:
pn_message_set_durable(message, true);
for(i=0;i<10;i++){
gettimeofday(&start, NULL);
pr
I am able to get persistence working. Thanks guys.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/How-to-config-c-broker-persistence-tp7605544p7606970.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
--
Thanks Frase. I installed libdb5.1++dev, after that cmake shows
cmake ..
-- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
-- BerkeleyDB for C++, libaio and uuid found, Legacystore support enabled
-- Legacystore is excluded from build.
-- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb
Thanks for the reply.
This is what I have.
cmake ..
-- Qpid proton found, amqp 1.0 support enabled
-- Legacystore requires BerkeleyDB for C++ which is absent.
-- Legacystore is excluded from build.
-- Linearstore requires BerkeleyDB for C++ which is absent.
-- Linearstore is excluded from build.
It turns out the /etc/sasl2/qpidd.conf comes from the apt-get install qpidd
pointing to a different db location. Change that address the SASL issue.
But still I cannot get the link working. I end up writing a shovel program
that fetches messages from local queue and resend them to Azure.
--
V
I do not see too much documentation (not in README, INSTALL, and runbook)
about persistence. Google qpid persistence leads to the components site,
that's why I check it out and try to build.
If it is already with the 0.26 release, that is great.
So I have this in my /etc/qpid/qpidd.conf, assumei
I svn checkout the persistence store package. After ./bootstrap, I always get
this error message.
./configure --with-qpid-build ~/qpid-cpp-0.26/build
./configure --with-qpid-checkout ~/qpid-cpp-0.26/
./configure --with-qpid-prefix ~/qpid-cpp-0.26/
checking build system type... Invalid configurati
Thanks for the reply. I managed to get SASL start with the broker by
rebuilding. However, when I test with proton, it failed with these logs.
my endpoint
amqp://test:test1@127.0.0.1:5672/myqueue
send exe output:
recv: Connection refused
[0x99e830]:ERROR[-2] SASL header mismatch: ''
I do have a u
Thanks for the help.
installed this
sudo apt-get install libsasl2-dev
Unfortunately still have the same issue:
cmake ..
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- Could NOT find VALGRIND (missing: VALGRIND_EXECUTABLE)
-- Could NOT find SASL (missing: FOUND_SASL_LIB FOUND_SASL_H)
This may be related:
When I turn on authN
/etc/qpidd.conf
auth=yes
realm=QPID
I got
sudo src/qpidd --daemon --config /etc/qpidd.conf --load-module amqp.so
--log-to-stdout yes --log-to-syslog yes --log-enable info+ --data-dir
/var/qpiddata
[Broker] critical Unexpected error: Requested authenticati
Thanks for the reply, it is helpful. Ran into an issue with qpid-config add
outgoing my-out-link.
This is fine:
qpid-config -b 127.0.0.1:5672 add domain my-servicebus --argument
url=mynamespace.servicebus.windows.net --argument username=myusername
--argument password=mypassword= --argument sasl_me
Thanks for the reply. Would you please elaborate more as both support amqp
1.0?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Does-broker-federation-work-with-azure-service-bus-tp7605140p7605145.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
We need post some messages to Azure Service Bus and figure it would be nice
(in case Azure service bus is down) to post messages to the local qpid
broker first and then let the broker propagate messages to Azure.
I tried with
qpid-route -d queue add azureuser/passw...@namespace.servicebus.windo
20 matches
Mail list logo
