Are you able to test by building the client yourself from the current trunk sources?
Prefetch shouldn't have any effect, it's just that a prior fix to allow for proper recover() with client ack hadn't properly taken into account the onMessage() case. Hopefully the small change I applied here: https://svn.apache.org/viewvc?view=revision&revision=r1630766 should solve that issue. As an aside, proton-j itself doesn't provide any direct asynchronous API, so you'd have to build one... and since I think the bug in the JMS client is restricted to the async case (and receive should work fine) I don't think that would help you. However if you do plan to use the JMS client, I'd strongly recommend picking up the latest release (0.30) as that has a number of bug fixes in it (although sadly not one for the particular bug you have encountered :-( ... that fix will be going in to 0.32). -- Rob On 10 October 2014 13:48, jonathans2 <[email protected]> wrote: > Hi, > Yes, this was using an asychronous messagelistener. If relevant, I'm also > using the fairly special case of having prefetch=1, not sure if that has > any > impact on the bug. > > Thanks for the quick attention! > > Jonathan > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Problems-using-CLIENT-ACKNOWLEDGE-with-qpid-amqp-1-0-client-jms-0-28-and-ActiveMQ-tp7614874p7614887.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
