From commits-return-2668-apmail-ace-commits-archive=ace.apache.org@ace.apache.org Fri Feb 15 14:57:14 2013 Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6637AE3CA for ; Fri, 15 Feb 2013 14:57:14 +0000 (UTC) Received: (qmail 74053 invoked by uid 500); 15 Feb 2013 14:57:14 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 73450 invoked by uid 500); 15 Feb 2013 14:57:13 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 73384 invoked by uid 99); 15 Feb 2013 14:57:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2013 14:57:13 +0000 Date: Fri, 15 Feb 2013 14:57:13 +0000 (UTC) From: "Marcel Offermans (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACE-318) HTTP sessions don't expire MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579226#comment-13579226 ] Marcel Offermans commented on ACE-318: -------------------------------------- I'm going to implement solution #2 for now. > HTTP sessions don't expire > -------------------------- > > Key: ACE-318 > URL: https://issues.apache.org/jira/browse/ACE-318 > Project: ACE > Issue Type: Bug > Components: UI > Reporter: Marcel Offermans > Assignee: Marcel Offermans > > After some debugging and reading, I discovered that our HTTP sessions by default have a timeout of 0, which means they never expire. Why this is the default I'm not sure but we should fix this, because if you create enough sessions, you will now run out of memory. Two solutions are possible: > 1) Use the development version of the Felix HTTP service, which does have support for configuring the timeout. Actually the documentation already mentions this, it just fails to mention that the latest release does not yet support that option. > 2) Explicitly use setMaxInactiveInterval(secs) on each session we create. Provided we can hook into each location where sessions are created, this should work too, and won't require us upgrading to some snapshot version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira