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

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

Working trace with same route returned for 2 requests:
Connection request: [route: {s}->https://10.2.21.147:8443][total kept alive: 0; 
route allocated: 0 of 50; total allocated: 0 of 200]
Connection leased: [id: 0][route: {s}->https://10.2.21.147:8443][total kept 
alive: 0; route allocated: 1 of 50; total allocated: 1 of 200]
Connection [id: 0][route: {s}->https://10.2.21.147:8443] can be kept alive for 
30000 MILLISECONDS
Connection released: [id: 0][route: {s}->https://10.2.21.147:8443][total kept 
alive: 1; route allocated: 1 of 50; total allocated: 1 of 200]
Connection request: [route: {s}->https://10.2.21.147:8443][total kept alive: 1; 
route allocated: 1 of 50; total allocated: 1 of 200]
Connection leased: [id: 0][route: {s}->https://10.2.21.147:8443][total kept 
alive: 0; route allocated: 1 of 50; total allocated: 1 of 200]
Connection [id: 0][route: {s}->https://10.2.21.147:8443] can be kept alive for 
30000 MILLISECONDS
Connection released: [id: 0][route: {s}->https://10.2.21.147:8443][total kept 
alive: 1; route allocated: 1 of 50; total allocated: 1 of 200]
Connection manager is shutting down
Connection manager shut down

Not working trace with a new route returned whereas same request is sent again:
Connection request: [route: {s}->https://10.2.21.147:8443][total kept alive: 0; 
route allocated: 0 of 50; total allocated: 0 of 200]
Connection leased: [id: 0][route: {s}->https://10.2.21.147:8443][total kept 
alive: 0; route allocated: 1 of 50; total allocated: 1 of 200]
Connection [id: 0][route: {s}->https://10.2.21.147:8443][state: 
CN=KMSClientKeyPair, OU=PSE, O=O, L=G, C=FR] can be kept alive for 30000 
MILLISECONDS
Connection released: [id: 0][route: {s}->https://10.2.21.147:8443][state: 
CN=KMSClientKeyPair, OU=PSE, O=O, L=G, C=FR][total kept alive: 1; route 
allocated: 1 of 50; total allocated: 1 of 200]
Connection request: [route: {s}->https://10.2.21.147:8443][total kept alive: 1; 
route allocated: 1 of 50; total allocated: 1 of 200]
Connection leased: [id: 1][route: {s}->https://10.2.21.147:8443][total kept 
alive: 1; route allocated: 2 of 50; total allocated: 2 of 200]
Connection [id: 1][route: {s}->https://10.2.21.147:8443][state: 
CN=KMSClientKeyPair, OU=PSE, O=O, L=G, C=FR] can be kept alive for 30000 
MILLISECONDS
Connection released: [id: 1][route: {s}->https://10.2.21.147:8443][state: 
CN=KMSClientKeyPair, OU=PSE, O=O, L=G, C=FR][total kept alive: 2; route 
allocated: 2 of 50; total allocated: 2 of 200]
Connection manager is shutting down
Connection manager shut down
                
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to