You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Rémi Kowalski (Jira)" <se...@james.apache.org> on 2019/11/06 09:09:00 UTC
[jira] [Updated] (JAMES-2966) es-report thread leak upon close
[ https://issues.apache.org/jira/browse/JAMES-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rémi Kowalski updated JAMES-2966:
---------------------------------
Description:
The previous elastic-search-metrics-reporter had some threads leaks when reporting metrics.
It was due to the elastic serach metrics reporter librairy (mis) using HTTPConnectionURL where some connection where left open and thus leaked threads.
The PR fixed this in the librairy is : https://github.com/linagora/elasticsearch-metrics-reporter-java/pull/8
Upgrade to the new version fixing this issues
was:
The previous elastic-search-metrics-reporter had some threads leaks.
Upgrade to the new version fixing this issues
> es-report thread leak upon close
> --------------------------------
>
> Key: JAMES-2966
> URL: https://issues.apache.org/jira/browse/JAMES-2966
> Project: James Server
> Issue Type: Bug
> Reporter: Rémi Kowalski
> Priority: Major
>
> The previous elastic-search-metrics-reporter had some threads leaks when reporting metrics.
> It was due to the elastic serach metrics reporter librairy (mis) using HTTPConnectionURL where some connection where left open and thus leaked threads.
> The PR fixed this in the librairy is : https://github.com/linagora/elasticsearch-metrics-reporter-java/pull/8
> Upgrade to the new version fixing this issues
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org