[jira] [Commented] (CALCITE-6530) HTTP Sessions are never expired in Avatica server

["Istvan Toth (Jira)" <ji...@apache.org>]

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

Istvan Toth commented on CALCITE-6530:
--------------------------------------

Fixed in [452df113cf85cde5baf5bf7d67d8a014b81a92af|https://github.com/apache/calcite-avatica/commit/452df113cf85cde5baf5bf7d67d8a014b81a92af]

 

> 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)