[jira] [Updated] (GEODE-6535) ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) ignore their timeout parameter
[ https://issues.apache.org/jira/browse/GEODE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo updated GEODE-6535: -- Labels: pull-request-available (was: needs-review pull-request-available) > ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) > ignore their timeout parameter > > > Key: GEODE-6535 > URL: https://issues.apache.org/jira/browse/GEODE-6535 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Darrel Schneider >Assignee: Mario Kevo >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The ConnectionManagerImpl methods exchangeConnection and > borrowConnection(ServerLocation) both have a timeout parameter that they > simply ignore. > They should either honor the timeout by waiting for an existing connection or > they should not take a timeout parameter. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6535) ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) ignore their timeout parameter
[ https://issues.apache.org/jira/browse/GEODE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo updated GEODE-6535: -- Labels: needs-review pull-request-available (was: pull-request-available) > ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) > ignore their timeout parameter > > > Key: GEODE-6535 > URL: https://issues.apache.org/jira/browse/GEODE-6535 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Darrel Schneider >Assignee: Mario Kevo >Priority: Major > Labels: needs-review, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The ConnectionManagerImpl methods exchangeConnection and > borrowConnection(ServerLocation) both have a timeout parameter that they > simply ignore. > They should either honor the timeout by waiting for an existing connection or > they should not take a timeout parameter. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6535) ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) ignore their timeout parameter
[ https://issues.apache.org/jira/browse/GEODE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo updated GEODE-6535: -- Labels: needs-review (was: ) > ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) > ignore their timeout parameter > > > Key: GEODE-6535 > URL: https://issues.apache.org/jira/browse/GEODE-6535 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Darrel Schneider >Assignee: Mario Kevo >Priority: Major > Labels: needs-review > Time Spent: 10m > Remaining Estimate: 0h > > The ConnectionManagerImpl methods exchangeConnection and > borrowConnection(ServerLocation) both have a timeout parameter that they > simply ignore. > They should either honor the timeout by waiting for an existing connection or > they should not take a timeout parameter. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6535) ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) ignore their timeout parameter
[ https://issues.apache.org/jira/browse/GEODE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo updated GEODE-6535: -- Labels: needs-review pull-request-available (was: needs-review) > ConnectionManagerImpl exchangeConnection and borrowConnection(ServerLocation) > ignore their timeout parameter > > > Key: GEODE-6535 > URL: https://issues.apache.org/jira/browse/GEODE-6535 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Darrel Schneider >Assignee: Mario Kevo >Priority: Major > Labels: needs-review, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The ConnectionManagerImpl methods exchangeConnection and > borrowConnection(ServerLocation) both have a timeout parameter that they > simply ignore. > They should either honor the timeout by waiting for an existing connection or > they should not take a timeout parameter. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
