Re: Set destination from Qpid Proton Client

[MattR]

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; albeit with a mangled name for the queue
(e.g. qpidsub_/ID:). The mangled name was my problem as I needed the
name to match the binding key so as to prevent unnecessary extra queues
(i.e. a queue with name "test_queue" could be found in the amq.direct
exchange with destination and bindingKey both set to "test_queue"). I have
gotten around this by simply utilizing the REST api to create the queue and
exchange binding on the fly (based on our current code, this used to be
possible using the old Python Qpid api's session.declare_queue and
session.exchange_bind, respectively).

My issue now is that I, essentially, need to be able to do the following in
Proton:

# Declare a local queue to which we subscribe the reply-to queue
localQueueName = "producerLocalQueue_" + session.name
localQueue = session.incoming(localQueueName)
session.message_subscribe(queue=replyQueueName,
  destination=localQueueName)
localQueue.start()

(ref: https://www.linuxjournal.com/article/10379)

I can't seem to figure out how to mimic the message_subscribe behavior. Is
that simply creating another receiver passing the reply queue as the source
and local queue as the target or name?

I apologize in advance if I'm making this over complicated or missing
something from the docs/api that explain this.

Thanks,

Matt R.



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)

[Ganesh Murthy]

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 fixes are introduced in 1.8.0:

Features -
   DISPATCH-1337 - Fallback Destination for Unreachable Addresses

Improvements -
DISPATCH-1308 - Console access to the force-close a connection feature
DISPATCH-1320 - Make it easier to use separate logos for upstream
and downstream masthead
DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies)
when they are found in nonstandard location
DISPATCH-1329 - Edge router system test needs skip test convenience switches
DISPATCH-1340 - Show settlement rate and delayed deliveries in client popup
DISPATCH-1341 - Add list of delayed links to console's overview page
DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary
DISPATCH-1356 - Remove the dotted line around routers that
indicates the router is fixed.
DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close'

Bug fixes -
DISPATCH-974 - Getting connections via the router management
protocol causes AMQP framing errors
DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - system_tests_ssl
DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL
DISPATCH-1317 - HTTP system test is failing on python2.6
DISPATCH-1318 - edge_router system test failing
DISPATCH-1322 - Edge router drops disposition when remote receiver closes
DISPATCH-1323 - Deprecate addr and externalAddr attributes of
autoLink entity. Add address and externalAddress instead.
DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function
DISPATCH-1325 - Sender connections to edge router that connect
'too soon' never get credit
DISPATCH-1326 - Anonymous messages are released by edge router
even if there is a receiver for the messages
DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count
decrement on link detach
DISPATCH-1334 - Background map on topology page incorrect height
DISPATCH-1335 - After adding client, topology page shows new icon
in upper-left corner
DISPATCH-1339 - Multiple consoles attached to a router are showing
as separate icons


Thanks.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Broker-J topic example with rhea.js

[Rob Godfrey]

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":
>
> 
>
> Then I created a publisher with rhea.js: https://pastebin.com/4MWe1Qgh it
> is
> a modified version of the rhea.js  publisher
> <
> https://github.com/amqp/rhea/blob/master/examples/durable_subscription/publisher.js>
>
> and  subscriber
> <
> https://github.com/amqp/rhea/blob/master/examples/durable_subscription/subscriber.js>
>
> example.
>
> Unfortunately it doesn't work, a Could not find destination for target
> 'Target{address=objects.bed.update,durable=none}' error is thrown:
> https://pastebin.com/AifSYHGs
>
> Can anybody please help me with figuring out which host name and topic name
> to use? Any help would be appreaciated!
>
> Best regards
> Tobi
>
>
"objects.bed.update" is a binding to amq.topic, it is not an an address in
itself.

You should be able to send to the address "amq.topic/objects.bed.update"
(i.e. /) to achieve what you want

-- Rob


>
>
> --
> Sent from:
> http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Broker-J topic example with rhea.js

[fea17e86]

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 rhea.js: https://pastebin.com/4MWe1Qgh it is
a modified version of the rhea.js  publisher

  
and  subscriber

  
example.

Unfortunately it doesn't work, a Could not find destination for target
'Target{address=objects.bed.update,durable=none}' error is thrown:
https://pastebin.com/AifSYHGs

Can anybody please help me with figuring out which host name and topic name
to use? Any help would be appreaciated!

Best regards
Tobi



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[RESULT][VOTE] Release Apache Qpid JMS 0.43.0

[Robbie Gemmell]

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

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: sender.close() hangs

[Gordon Sim]

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 sender.close() procedure application hangs and no error
nor trace is shown. We have enable debugging and nothing is seen.

Besides, in the server.cpp example provided in qpid-cpp the same problem
happens.

Anyone knows what it is the problem?


Can you get a protocol trace? E.g. set env var QPID_LOG_ENABLE=trace+ 
when running the client.


That will show the interaction with the broker on closing a sender link 
and hopefully some insight into the problem.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.43.0

[Keith W]

+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
-DskipTests=true -DskipITs=false) against the staged Maven artefacts

On Wed, 5 Jun 2019 at 12:29, Oleksandr Rudyy  wrote:
>
> +1
>
> * verified checksums and signatures
> * built and ran tests successfully from source bundle
> * ran successfully Qpid Broker-J integration tests on master using staged
> artefacts
>
>
> On Tue, 4 Jun 2019 at 13:09, Robbie Gemmell 
> wrote:
>
> > Hi folks,
> >
> > I have put together a spin for a 0.43.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms/0.43.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1177
> >
> > The JIRAs assigned are:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12345485
> >
> > Regards,
> > Robbie
> >
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> >
> >   
> > 
> >   staging
> >   
> > https://repository.apache.org/content/repositories/orgapacheqpid-1177
> > 
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.43.0
> >   
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org