Bug 1016552 - Connection level max_prefetch doesn't work as required with qpid-jca
Summary: Connection level max_prefetch doesn't work as required with qpid-jca
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-jca
Version: 2.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 10:42 UTC by Valiantsina Hubeika
Modified: 2025-02-10 03:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:28:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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

Comment 6 Red Hat Bugzilla 2025-02-10 03:28:41 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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