ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Resolved] (ACE-318) HTTP sessions don't expire
Date Mon, 18 Feb 2013 11:23:13 GMT


Marcel Offermans resolved ACE-318.

    Resolution: Fixed

All HTTP sessions in the web UI now expire after 2 minutes of inactivity. The REST UI does
not use HTTP sessions. It does manage "workspaces" which need to be cleaned up. For now we
are not automatically expiring those, but we could consider that as well.
> HTTP sessions don't expire
> --------------------------
>                 Key: ACE-318
>                 URL:
>             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:

View raw message