Meant to add, folks should use the users list for posts like this as thats
what its for, theres a bigger audience to answer things, and there isnt
dev-related traffic that can often drown out individual posts like this.
On 10 May 2018 at 16:54, Robbie Gemmell wrote:
>
The issue is known in that it was discovered previously and resolved in the
0.23.0 release last year, via
https://issues.apache.org/jira/browse/QPIDJMS-292. As you also seem to have
identified, a workaround is setting the prefetch to 1 (or zero for newer
clients). We dont have any plans for more
Sorry, the version we are using is 0.11.1, not 0.11.0.
Il 10/05/2018 15:41, Alessandro Crotti - SMC Consulting ha scritto:
Hello,
Using Qpid JMS 0.11.0 AMQP 1.0 client, which is the latest version for
Java 7, we experienced an issue when you set prefetch > 1 and start
consuming messages
Hello,
Using Qpid JMS 0.11.0 AMQP 1.0 client, which is the latest version for
Java 7, we experienced an issue when you set prefetch > 1 and start
consuming messages from a queue in asynchronous mode, using
"onMessage()" method and sessionMode = Session.CLIENT_ACKNOWLEDGE.
Taking prefetch=