Session data cleanup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install FluxCP
2. Let 'er run for a couple of weeks

What is the expected output? What do you see instead?
The session data used to keep track of session information becomes very,
very full.  After one month of hits on a low-volume server, the session
data has exceeded 400MB.  On a high volume server, this would consume
gigabytes of disk space.

What version of the product are you using? On what operating system?
Latest trunk.

Please provide any additional information below.

Original issue reported on code.google.com by neve...@gmail.com on 1 Jul 2009 at 9:22

[GoogleCodeExporter]

Confirmed. Session data isn't purged after an amount of time.
This can be a show shopper for very large servers that get many hits.
It could also be generated into a form of attack, albeit a poor and 
time-consuming
one that could be easily circumvented and won't be a show stopper for too long.

Original comment by Paradox924X on 15 Jul 2009 at 4:47

• Changed state: Accepted
• Added labels: Performance, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by Paradox924X on 1 Jul 2011 at 9:56

• Changed state: Fixed
• Added labels: Usability