You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2024/08/15 05:54:00 UTC
[jira] [Resolved] (CALCITE-6530) HTTP Sessions are never expired in Avatica server
[ https://issues.apache.org/jira/browse/CALCITE-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth resolved CALCITE-6530.
----------------------------------
Fix Version/s: avatica-1.26.0
Resolution: Fixed
> HTTP Sessions are never expired in Avatica server
> -------------------------------------------------
>
> Key: CALCITE-6530
> URL: https://issues.apache.org/jira/browse/CALCITE-6530
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
> Fix For: avatica-1.26.0
>
>
> Http Sessions created by the Avatica server are never expired.
> This eventually causes the Avatica server to OOM.
> Well designed clients using long-lived sessions may never generate enough sessions between server restarts for this to become apparent, but ill-behaved clients creating a lot of sessions can fill the heap in a short time.
> As the Jetty default (when not using the web.xml descriptor) is infinite lifetime, we need to set a reasonable default idle timeout when setting up Jetty Session handling.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)