[JIRA] Updated: (SIDP-537) Non-closed connections when using FileBackedHTTPMetadataProvider (metadata / attribute filters)

[Chad La Joie (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SIDP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie updated SIDP-537:
------------------------------

    Summary: Non-closed connections when using FileBackedHTTPMetadataProvider (metadata / attribute filters)  (was: Non-closed connections when using HttpResources (metadata / attribute filters))

> Non-closed connections when using FileBackedHTTPMetadataProvider (metadata / attribute filters)
> -----------------------------------------------------------------------------------------------
>
>                 Key: SIDP-537
>                 URL: https://issues.shibboleth.net/jira/browse/SIDP-537
>             Project: Shibboleth IdP 2 - Java
>          Issue Type: Improvement
>    Affects Versions: 2.3.5
>         Environment: Tomcat 6.0.35, Java 1.6.0_24, and some firewall between the IdP and the web server serving the files
>            Reporter: Patrik Schnellmann
>            Assignee: Chad La Joie
>            Priority: Minor
>
> The IdP does not close the connections after retrieving metadata or other files via HTTP(s), even when the connection was terminated from the server's side. The effect was observed on the firewall, where FIN packets were sent from the IdP about an hour after the connection had been opened. The IdP seems to want to reuse the connection after one hour roughly and when this fails, the FIN packets are sent. The time period may depend on the refresh interval configured on the IdP - we use 1 hour for most deployments. The effect was seen from a number of clients that retrieved metadata from our web server.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira