qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Updated: (QPID-895) FailoverSingleServer delays on first connection.
Date Mon, 05 May 2008 11:06:55 GMT

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

Martin Ritchie updated QPID-895:
--------------------------------

    Fix Version/s: M3

> FailoverSingleServer delays on first connection.
> ------------------------------------------------
>
>                 Key: QPID-895
>                 URL: https://issues.apache.org/jira/browse/QPID-895
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2.1, M3
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>            Priority: Minor
>             Fix For: M3
>
>         Attachments: FailoverSingleServer.patch.txt
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Summary:
> _currentRetries is -1 on first connection but at the delay point in getNextBroker it
has already been incremented.
> I'm sure the code was supposed to incorrectly say '-1' rather than '1' but both of those
are wrong. We want to delay on all subsequent connection attempts which means '> 0'. 
> -        if (delayStr != null && _currentRetries != 1)
> +       if (delayStr != null && _currentRetries > 0)
> So this should fix the issue. A work around is to use two brokers in the URL with their
own connectdelay that way it will use the RoundRobin Method which doesn't have this bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message