qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-1894) Incorrect/Unused URL options are not reported leading to confusion
Date Fri, 18 Jul 2014 21:52:06 GMT

     [ https://issues.apache.org/jira/browse/QPID-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Keith Wall resolved QPID-1894.

    Resolution: Won't Fix

Agreed in a product backlog review - won’t fix.

> Incorrect/Unused URL options are not reported leading to confusion
> ------------------------------------------------------------------
>                 Key: QPID-1894
>                 URL: https://issues.apache.org/jira/browse/QPID-1894
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2.1, M3, M4, 0.5
>            Reporter: Martin Ritchie
> Summary:
> This url will parse and will connect happily however the maxprefetch value is never used.
> amqp://u:p@client1/vhost?brokerlist='tcp://host:port?retries='10000'&connectdelay='5000'&connecttimeout='10000'&maxprefetch='10''
> The maxprefetch value is a connection option not a broker option.
> amqp://u:p@client1/vhost?brokerlist='tcp://host:port?retries='10000'&connectdelay='5000'&connecttimeout='10000''&maxprefetch='10'
> Potentially we should allow both as you may wish to change the prefetch based on the
network topology of the broker you are connected. Leaving the top level value in (potentially
renamed to defaultmaxprefetch) would also be of value so a user need not repeat the setting
for each broker.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message