Bug 972621 - After deleting queue enabling producer flow control, Java client cant still produce
Summary: After deleting queue enabling producer flow control, Java client cant still p...
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java   
(Show other bugs)
Version: 2.3
Hardware: All Linux
Target Milestone: 3.3
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
Keywords: TestCaseProvided
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-10 08:45 UTC by Pavel Moravec
Modified: 2018-02-06 16:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Pavel Moravec 2013-06-10 08:45:30 UTC
Description of problem:
Having a Java producer that is blocked by producer flow control due to queue X full and deleting such queue, the producer can't start to send messages further.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. java -Dmax_prefetch=10 org.apache.qpid.example.Spout -c=100000000 --content=<at_least_2k_content> "'amq.fanout'/None"
2. qpid-receive -a "amq.fanout" -f -m 1000000 --receive-rate=1
3. wait until amq.fanout_<uuid> queue gets full and producer flow control is enabled
4. Stop qpid-receive

Actual results:
Spout can't produce more messages despite it is not blocked by producer flow control.
(to check it: run qpid-stat -e periodically, amq.fanout exchange will have same msgIn counter)

Expected results:
Spout produces more messages.

Additional info:
The problem comes from Java client that sends session.flush, not from the broker.

Note You need to log in before you can comment on or make changes to this bug.