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

Tim Allison resolved TIKA-5064.
-------------------------------
    Fix Version/s: 4.3.0
       Resolution: Fixed

> When SaveFetcher is called regularly, resources leak
> ----------------------------------------------------
>
>                 Key: TIKA-5064
>                 URL: https://issues.apache.org/jira/browse/TIKA-5064
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Bartek Ciszkowski
>            Priority: Major
>             Fix For: 4.3.0
>
>
> HttpFetcher and AtlassianJwtFetcher both maintain HttpClients, but they never 
> close them. When SaveFetcher replaces or DeleteFetcher removes a fetcher, the 
> old instance is never closed, resulting in each client keeping a "Connector 
> evictor" thread alive
> This was discovered when a system calling tika would periodically call 
> SaveFetcher as a means of keeping fetchers in sync and preventing them from 
> going stale. Over time, the resources built up and Tika would OOM.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to