Bug 1016552

Summary: Connection level max_prefetch doesn't work as required with qpid-jca
Product: Red Hat Enterprise MRG Reporter: Valiantsina Hubeika <vhubeika>
Component: qpid-jcaAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.3CC: jross, mtoth
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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: --- Target Upstream Version:
Embargoed:

Description Valiantsina Hubeika 2013-10-08 10:42:33 UTC
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