-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.2
-
reproduced on (4 vCPU, 4GB ram)
RHEL 6 i686, x86_64
those are only platform where below scenario was created, this behavior/issue was observer generally
when queue on AMQ broker contains significant amount of messages (for example 500), and receiver try to read until queue is empty (msgs are available) without setting fetch timeout, it cannot read them all.