I was wondering ... how can the Qpid JMS client setup a selector which
would filter messages based on Correlation ID (and work against Qpid C++
broker)?
In the C++ Qpid Messaging API, the selector set like this:
amqp.correlation_id = 'f5b13484-5d85-4669-ac2f-53a85b2c8fe7'
seems to work fine.
But
Making my +1 explicit.
I gave things a kick of the tyres as follows:
- Verified the sigs and checksums.
- Checked the LICENCE and NOTICE files are present and look ok.
- Verified licence headers in src archive using: mvn apache-rat:check.
- Ran the build+tests from the src archive, all passed.
-
On 08/14/2015 08:47 AM, Robbie Gemmell wrote:
Hi all,
Its time for the 0.4.0 Qpid JMS client release, now that Proton 0.10
is available. I have put together a first spin, please test it and
vote accordingly.
The source and binary archives can be grabbed from here:
On 14 August 2015 at 15:37, Jakub Scholz ja...@scholz.cz wrote:
I was wondering ... how can the Qpid JMS client setup a selector which
would filter messages based on Correlation ID (and work against Qpid C++
broker)?
In the C++ Qpid Messaging API, the selector set like this:
Hi Robbie,
Thanks. You are right, double quotes help to solve this. I was quite close
when I tried single quotes, but they don't help. And trying double quotes
didn't come to my mind.
The compatibility issue across different brokers is for sure unfortunate.
Although it at least has a workaround.
On 14 August 2015 at 17:17, Jakub Scholz ja...@scholz.cz wrote:
Hi Robbie,
Thanks. You are right, double quotes help to solve this. I was quite close
when I tried single quotes, but they don't help. And trying double quotes
didn't come to my mind.
The compatibility issue across different
Hi all,
Its time for the 0.4.0 Qpid JMS client release, now that Proton 0.10
is available. I have put together a first spin, please test it and
vote accordingly.
The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.4.0-rc1/
Those files and
On 08/13/2015 07:50 AM, Haoliang Chen wrote:
So how can I ensure the message was transfer within the federation
successfully?
Simply put, the problem is if one broker was jammed by a slow receiver,
messages will be dropped between the source broker and the jammed broker
silently.
If you want
