Re: Set destination from Qpid Proton Client

My apologies for lacking detail. I'm certainly not trying to make anything more complicated than I need to. >From my understanding, there is no way to create a queue from the client. However, with Broker-J, if trying to subscribe to a non-existent queue, then Broker-J will create one for you;

[VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)

Hello All, Please cast your vote on this thread to release RC1 as the official Qpid Dispatch Router version 1.8.0. RC1 of Qpid Dispatch Router version 1.8.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ The following features, improvements, and bug

Re: Broker-J topic example with rhea.js

On Fri, 7 Jun 2019 at 16:24, fea17e86 wrote: > Hi, > > I'm trying to get a publish subscribe example with Broker-J and rhea.js > to work. > > First I created a few queues bound to the default exchange "amq.topic": > >

Broker-J topic example with rhea.js

Hi, I'm trying to get a publish subscribe example with Broker-J and rhea.js to work. First I created a few queues bound to the default exchange "amq.topic": Then I created a publisher with

[RESULT][VOTE] Release Apache Qpid JMS 0.43.0

There were 4 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. Robbie

Re: sender.close() hangs

On 06/06/2019 2:33 pm, Jose Alberto Fernandez Parejo wrote: Hello everyone, We are using rabbitmq broker and qpid-cpp last version API to send/receive messages to/from broker with AMQP1.0 Our application using several senders over the same connection and session. When calling to

Re: [VOTE] Release Apache Qpid JMS 0.43.0

+1 * Verified signatures and checksums * Checked for LICENCE and NOTICE files in the archives. * ran apache rat-check * built from source distribution artefact and ran all tests (mvn verify with Java 1.8.0_191 on Mac OS X 10.13.6) * ran Broker-J's JMS integration test suite (mvn clean verify