Hi Rob,
I've registered an account and opened JIRA QPID-5573
https://issues.apache.org/jira/browse/QPID-5573
I think you've already seen it.
I've attached the files I have "developed" for this test scenario. Shouldn't
be anything complicated. I'm not using an IDE or anything, so everything is
just command-line driven.
I'm not at work, so it was an effort to grab these files :)
Anyway, no rush - I'm not back in-office until Monday anyway.
Please let me know if there's more I can attach or provide, or if you need
more information on the test environment/scenario.
Thanks again,
Mark.
-----Original Message-----
From: Rob Godfrey
Sent: Thursday, February 20, 2014 5:49 PM
To: [email protected]
Subject: Re: New User JMS API Questions
On 21 February 2014 01:38, Rob Godfrey wrote:
On 21 February 2014 01:15, Mark Barker wrote:
Thanks for the help, Rob.
Here's some more feedback from today's experiments.
I tried the setDeliveryMode on my 'basic' producer client (AMQP 1.0
client interacting only with ActiveMQ 5.9.0 broker's AMQP transport
connector).
In so doing, I could use the Qpid 0.27 AMQP 1.0 API to send() without
hanging. A basic consumer client retrieved the message without issue.
Hmmm - it was OK with 0.26 but not 0.27 (trunk)... I'll have to look into
that then
On a second look, it does appear that the synchronous publishing fix (
https://issues.apache.org/jira/browse/QPID-5455) wasn't actually in 0.26...
so my guess would be that ActiveMQ is not sending back the required
synchronous response - although they did say they had tested it... I'll
have a go at testing with ActiveMQ tmr to confirm. If all else fails I can
always add in an option to revert to the original (incorrect) behaviour of
publishing asynchronously
-- Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
