Hello All,
I could solve the problem.
qpid-send is using amqp 0.10 by default but it needs to use amqp 1.0. Then
it works.
Kind Regards,
Andreas
Thanks for suggestions about naming of distribution bundles.
I am going to rename Qpid Broker-J distribution bundles and build new RC.
The source bundle will be renamed into
'apache-qpid-broker-j--src.tar.gz' and the contained source
directory will be renamed form 'qpid-java' into
'apache-qpid-br
Hello,
I would like to configure a HA cluster using the Qpid C++ message broker
1.36.0. In the handbook I read that rgmanager is neccessary.
When I try to install it on Ubuntu 16.04 it is not found. On a Fedora
installation it is also not found.
Is anyone here using the Qpid message broker in a
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
* QPID-8023 - [Broker-J] Remove com.google.code.findbugs:jsr305 dependency
* QPID-8024 - [B
I have used the qpid C++ broker in clusters. On RHEL 6. Works very well.
> -Original Message-
> From: andi welchlin [mailto:andi.welch...@gmail.com]
> Sent: Wednesday, November 08, 2017 12:00 PM
> To: users@qpid.apache.org
> Subject: HA Cluster using Qpid C++ Broker 1.36.0
>
> Hello,
>
>
rgmanager has been replaced by pacemaker on RHEL7, I'm not sure what is
available on Ubuntu. There is no out-of-the-box integration with pacemaker
or other cluster managers, but all that is needed is some configuration and
a couple of scripts to enable the cluster manager to start, stop and
promote
+1
* verified signatures and checksums
* built from source distribution and ran all tests
* started broker, created new queue and exchange using web management
console, bound new queue to new exchange
* successfully ran hello world example using legacy JMS client with
AMQP 0-9 and 0-10
* successfu
+1
* built from source and ran tests
* exercised management console to create vhosts, queues, exchanges, etc
* tested shared durable subscription functionality
On 8 November 2017 at 12:12, Oleksandr Rudyy wrote:
> +1
>
> * verified signatures and checksums
> * built from source distribution and