Thank you for pointing me to this. Appreciate it very
much!
--- Len Popp <[EMAIL PROTECTED]> wrote:
> There was a bug fix in 5.5.21 that may be the same
> problem as yours.
> Changelog:
>
http://tomcat.apache.org/tomcat-5.5-doc/changelog.html
> (scroll down to 5.5.21)
> Bugzilla:
>
http://issues.a
There was a bug fix in 5.5.21 that may be the same problem as yours.
Changelog: http://tomcat.apache.org/tomcat-5.5-doc/changelog.html
(scroll down to 5.5.21)
Bugzilla: http://issues.apache.org/bugzilla/show_bug.cgi?id=37356
--
Len
On Jan 15, 2008 1:39 PM, Eqbal <[EMAIL PROTECTED]> wrote:
> Than
Thanks Bill!
Is there a bug report I can look at for this? I tried
searching on the website but could not locate it.
Also to which version should I upgrade, a minor
upgrade or to major version 6?
I am going to have a hard time upgrading as one of the
third party proprietary package we use only sup
rker" <[EMAIL PROTECTED]>
Sent by: news <[EMAIL PROTECTED]>
01/14/2008 07:58 PM
Please respond to
"Tomcat Users List"
To
users@tomcat.apache.org
cc
Subject
Re: sessions not cleaned up after expiry
Caterpillar: Confidential Green Retain Until: 02/13/2008
"Eqbal" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> I am noticing the in one of our webapps sessions are
> not getting cleaned up long after they have expired.
> Our session expiry time is set to 30 min. I am using
> lambdaprobe to monitor the sessions and it appears
> t
Hello Martin,
I am not sure I understand where you are going with
this. I do have jmx enabled so I can see the memory
allocation charts alright (survivor, eden, old, per
gen, code cache etc.). I have my ms and mx set to
1024m, permgen is set to 64m min and 192m max.
The thing I do not understand
Get probe.war operational first and for memory status you will need to haveto
get jmx running
http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.htmlmake sure you
set JRE_HOME properlytake a look at the log file location
in my case I have everything deployed locally
http://localhost:80
Hi,
I am noticing the in one of our webapps sessions are
not getting cleaned up long after they have expired.
Our session expiry time is set to 30 min. I am using
lambdaprobe to monitor the sessions and it appears
that all of these sessions contain one attribute,
__lambda_probe_la_ip.
I am using T
