hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "restonica (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1208) PoolingClientConnectionManager give a new route even if keep-alive
Date Thu, 21 Jun 2012 18:33:42 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398714#comment-13398714
] 

restonica commented on HTTPCLIENT-1208:
---------------------------------------

Requests share the same HTTP Context. 
This problem only appear when a client certificate is asked from the server. In SSL without
the mutual authentication it works !
I think the bug is that the route is saved with the 'state' and when the next connection request
is asked without the state (see logs), so not found into the map of existing routes.
                
> PoolingClientConnectionManager give a new route even if keep-alive
> ------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1208
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1208
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.2 Final
>            Reporter: restonica
>
> A connection is kept with a route and a specific state, for example :
> Connection [id: 0][route: {s}->https://x.x.x.x:8443][state: CN=KeyPair, OU=OU, O=O,
L=Marseille, C=FR] can be kept alive for 30000 MILLISECONDS
> If a new connection with the same route is asked, for example:
> Connection request: [route: {s}->https://x.x.x.x:8443][total kept alive: 1; route
allocated: 1 of 50; total allocated: 1 of 200]
> then the connection manager will give a NEW route (with a new ID).
> If the first kept connection (see the beginning) does not contain the state, all is OK
and the connection manager give the same route as the previous one.
> This bug cause problem in case of SSL mutual authentication, a new TCP connection is
done for each request !!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message