I agree that session recycling can be a security problem but am concerned
that removing recycling will significantly increase GC overhead. I would
like to see some before and after GC data from testing where 1000's of sessions
get used per hour. Testing with different versions of the JVM would be
+1
The session is a long-lived object, so the improvement on recycling is
minor.
Costin
Remy Maucherat wrote:
> Hi,
>
> I'd like to completely remove session recycling code from TC 5, as it is
> a potentially dangerous feature (which has been disabled in TC 4.1.x)
> and does not bring any ac
- Original Message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, July 07, 2003 2:54 PM
Subject: [5.0] Removing session recycling code
> Hi,
>
> I'd like to completely remove
I'd like to completely remove session recycling code from TC 5, as it
is a potentially dangerous feature (which has been disabled in TC
4.1.x) and does not bring any actual performance improvement while
using memory.
The biggest impact of the change is the removal of the recycled array
list for
Hi,
I'd like to completely remove session recycling code from TC 5, as it is
a potentially dangerous feature (which has been disabled in TC 4.1.x)
and does not bring any actual performance improvement while using memory.
The biggest impact of the change is the removal of the recycled array
list
