Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of robbie.gemmell@gmail.com
 designates 209.85.214.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACsaS96_65y=Gc_pdaTEBnqMU0=R96ER=p6Lgr4uKX6qiFtdZQ@mail.gmail.com>
References: <FCA69B10-C0E7-4021-847B-AE84BE1BBCAF@shaw.ca>
	<8EBC52B8DD984F48A6AE9BF0A99EE9E2@MBDESK4>
	<CAFitrpRfonYXpJdhW14y0D3B3FW_RJ65b-Ou51-tGr=CAjPyUA@mail.gmail.com>
	<7C6F20A8FE5940E98914A9E4CBDF572B@MBDESK4>
	<CAFitrpS6bNT9cgb2wqZn1ErZnH037YX2cq2LQ5cf1S0Ynzh4Cg@mail.gmail.com>
	<AAB7DEFF11D94569A1743E7AAB08353D@MBDESK4>
	<CACsaS97ZQBziOGmKh=k3FviQkzsNQx3N+S9LkQcZFgPAUco_Qw@mail.gmail.com>
	<C11A3BB3F37B44A4B6812C34E843D732@MBDESK4>
	<CACsaS97+axUL9-s010+sfPmqQsLoq1hjzPu+9vVzLF47hNJrow@mail.gmail.com>
	<33AEDF8E-67DB-4E6D-835B-7219DE5A9C76@shaw.ca>
	<CACsaS94VT7uXdJUN95SvY3Jy1tPYZTQqkss9fZCHjB182EaVrg@mail.gmail.com>
	<CACsaS94DE49ZeQwvZ-mQkVVxZ8i-BDxM1_TsoNGey33HL9SYFQ@mail.gmail.com>
	<CACsaS96fYtHU3QAf8NWSsm-015ZpeZqpW5KvdSdKUciqmyOEGA@mail.gmail.com>
	<CAFitrpR6Zs2zwMDJOz1cfvKxgL9dqfYTB_ixND=xq=MAFsxN2A@mail.gmail.com>
	<28F74BF178E140EB990948B79E16954F@MBDESK4>
	<CACsaS95ZhcWUg5o6GKofbyYLnKStu4mD0=yJtbd-v0Nhfke6PQ@mail.gmail.com>
	<CACsaS95UGABxF-XqR5tgtb-xbcx4VKudz5VFQLFFQ7wEow=i1g@mail.gmail.com>
	<A158B9B4-7A79-48A3-AD67-95E04834FD46@shaw.ca>
	<CACsaS962y9mEts-6tfod9FuPJJFHQ3F6Mqikt5hiZqVSLskM6A@mail.gmail.com>
	<CACsaS96_65y=Gc_pdaTEBnqMU0=R96ER=p6Lgr4uKX6qiFtdZQ@mail.gmail.com>
Date: Fri, 21 Feb 2014 02:00:04 +0000
Message-ID: 
 <CAFitrpS2ZaCFW0RH7=_vbffDH-0iNLnxX=1OByawNiYxD6fzfw@mail.gmail.com>
Subject: Re: New User JMS API Questions
From: Robbie Gemmell <robbie.gemmell@gmail.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Content-Type: multipart/alternative; boundary=f46d041c60f604f95204f2e0fb21

--f46d041c60f604f95204f2e0fb21
Content-Type: text/plain; charset=ISO-8859-1

The patch was indicated to have been tested against the ActiveMQ trunk /
5.10-SNAPSHOT, so something probably changed on the ActiveMQ side since
5.9.0 was released.

Probably this: https://issues.apache.org/jira/browse/AMQ-4741

Robbie

On 21 February 2014 00:49, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:

> On 21 February 2014 01:38, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:
>
> >
> >
> >
> > On 21 February 2014 01:15, Mark Barker <mark.barker@shaw.ca> 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
>

--f46d041c60f604f95204f2e0fb21--