On 7 March 2017 at 16:53, Vince Cole wrote:
> Hi Rob
>
> I guess I'm a bit confused too.
>
> I need to use JMS and AMQP 1.0, thought I was using the correct
> dependencies, as underneath they use proton-j, but now I'm not so sure.
>
>
qpid-amqp-1-0-client-jms is an
The current AMQP 1.0 JMS client, qpid-jms-client, does use proton-j.
The older qpid-amqp-1-0-client-jms does not use proton.
If you are using maven, look at http://qpid.apache.org/maven.html for
the current dependency detail. The current release is 0.20.0, and
0.21.0 should enter the release
On 7 March 2017 at 15:57, Vince Cole wrote:
> Hi Tim
>
> Thanks
>
> I now see that my client should be setting *jms.forceSyncSend=true*
> (although the ActiveMQ documentation has it as *jms.alwaysSyncSend=true*, so
> I am setting both) option in the connection URI.
Dont
Hi Tim
Thanks
I now see that my client should be setting *jms.forceSyncSend=true*
(although the ActiveMQ documentation has it as *jms.alwaysSyncSend=true*, so
I am setting both) option in the connection URI.
However, it is still operating asynchronously.
I forgot to mention that I am using
Hi Rob
I guess I'm a bit confused too.
I need to use JMS and AMQP 1.0, thought I was using the correct
dependencies, as underneath they use proton-j, but now I'm not so sure.
I'll see what happens if I pull either of the client libraries out...
--
View this message in context:
I have a requirement to for my JMS client to block, and only return once
the message has been accepted onto the specified queue or topic. If the
message is not accepted, then an exception should be thrown. We don't care
whether anything actually consumes the message.
However, my client can only
Hi Vince,
On 7 March 2017 at 15:21, Vince Cole wrote:
>
>
> I am using:
> * javax.jms : javax.jms-api : 2.0.1
> * org.apache.qpid : qpid-jms-client : 0.11.1
> * org.apache.qpid : qpid-amqp-1-0-client-jms : 0.32
>
I'm a bit confused by this: qpid-jms-client and
On 03/07/2017 09:21 AM, Vince Cole wrote:
I have a requirement to for my JMS client to block, and only return once
the message has been accepted onto the specified queue or topic. If the
message is not accepted, then an exception should be thrown. We don't care
whether anything actually consumes
I have a requirement to for my JMS client to block, and only return once
the message has been accepted onto the specified queue or topic. If the
message is not accepted, then an exception should be thrown. We don't care
whether anything actually consumes the message.
However, my client can only