Bug 1016552 - Connection level max_prefetch doesn't work as required with qpid-jca
Connection level max_prefetch doesn't work as required with qpid-jca
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-jca (Show other bugs)
2.3
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Ted Ross
Eric Sammons
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-08 06:42 EDT by Valiantsina Hubeika
Modified: 2015-01-04 17:57 EST (History)
3 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Valiantsina Hubeika 2013-10-08 06:42:33 EDT
Description of problem:

Client does not respond to the max_prefetch option set at the connection level as

<config-property name="connectionURL">amqp://guest:guest@client/test?max_prefetch='1000'&amp;brokerlist='tcp://192.168.122.67:5672?sasl_mechs='PLAIN''</config-property>


Please note that in case of JVM level max_prefetch, the option works as required


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

How reproducible:
100%

Steps to Reproduce:
1. create client on the provided connection factory with no transactions
2. read more than 500 messages

Actual results:

Client is able to read only 500 messages

Expected results:

Client reads up to 1000 messages

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