f the ssltimeout is 86400 seconds ie 1 day. It cannot be
changed with a property (on Java5).
Regards
Jeff MAURY
Caldarale, Charles R wrote:
>
>> From: Yuval Perlov [mailto:[EMAIL PROTECTED]
>> Subject: Re: ssl.SessionId Cache keeps growing
>
>> Been all over those object
> From: Yuval Perlov [mailto:[EMAIL PROTECTED]
> Subject: Re: ssl.SessionId Cache keeps growing
> Been all over those objects thinking I can set a system
> wide default.
There is the JVM -XX:SoftRefLRUPolicyMSPerMB=n option, where n is
defined as "Number of milliseconds per MB
> From: Jonadan [mailto:[EMAIL PROTECTED]
> Subject: Re: ssl.SessionId Cache keeps growing
>
> There are alternative designs than using sessions!
Not in this case. Don't confuse HTTPSession with SSLSession - the
former is managed by Tomcat and can be avoided as you state, the
server side telling
> you which user is actually sending the request.
>
--
View this message in context:
http://www.nabble.com/ssl.SessionId-Cache-keeps-growing-tp14999824p15014379.html
Sent from the Tomcat - User mailing l
On Jan 21, 2008, at 11:50 PM, Caldarale, Charles R wrote:
From: Yuval Perlov [mailto:[EMAIL PROTECTED]
Subject: ssl.SessionId Cache keeps growing
1. Any one has ever met this problem?
I haven't, but it's definitely an interesting one.
2. Is there anyway to access the ssl.Sessio
o system may have to keep session objects for
long.
For this reason, I always avoid to use sessions. If this is a major
problem
for you, alternative techniques might be worth trying!
Regards.
--
View this message in context: http://www.nabble.com/ssl.SessionId-
Cache-keeps-growing-tp14
major problem
for you, alternative techniques might be worth trying!
Regards.
--
View this message in context:
http://www.nabble.com/ssl.SessionId-Cache-keeps-growing-tp14999824p15010907.html
Sent from the Tomcat - User mailing list archive at Nabbl
> From: Yuval Perlov [mailto:[EMAIL PROTECTED]
> Subject: ssl.SessionId Cache keeps growing
>
> 1. Any one has ever met this problem?
I haven't, but it's definitely an interesting one.
> 2. Is there anyway to access the ssl.SessionId object and invalidate
> it d
This is a tricky one so bare with me...
We are using Tomcat 5.5 on windows running Java SSL. There are MANY
concurrent clients using SSL.
After investigating what seemed to be a memory leak and taking a
memory dump we realized that the memory is not leaking but rather
growing with a SoftR
