You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/04/10 13:57:13 UTC

[jira] [Resolved] (CONNECTORS-1185) Bug in how HttpClient connection manager is used

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

Karl Wright resolved CONNECTORS-1185.
-------------------------------------
    Resolution: Fixed
      Assignee: Karl Wright

> Bug in how HttpClient connection manager is used
> ------------------------------------------------
>
>                 Key: CONNECTORS-1185
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1185
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: LiveLink connector, Lucene/SOLR connector, RSS connector, Web connector
>    Affects Versions: ManifoldCF 1.8.2, ManifoldCF 2.0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.9, ManifoldCF 2.1
>
>
> The HttpClient team informs me that the way we've been setting socket timeouts will basically silently do nothing.  This is because HttpClient will ONLY pay attention to socket and connection timeouts at the connection manager level.  That has implications for connection pooling also, since our connection management must now be in complete sync with our repository/output connection management.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)