"alesj" wrote : anonymous wrote :
| | What does the tomcat stats servlet say about the app
(http://lamia:8080/status?full=true)?
| |
|
| Where do I find status app? Is it a part of 'all' AS configuration?
|
It's part of the jbossweb-tomcat55.sar/ROOT.war
| Welcome to JBoss
I have exactly the same problem, with Jboss 4.0.4 RC2
there seems to be a process that go check the session when it wants, not when
it should
On my dev server the sessions are destroyed in the good delay, but on my
production server, some of them seems to be never destoyed :(
View the original
anonymous wrote :
| What does the tomcat stats servlet say about the app
(http://lamia:8080/status?full=true)?
|
Where do I find status app? Is it a part of 'all' AS configuration?
Some info about AS, OS and Java
19:58:09,233 INFO [Server] Release ID: JBoss [Zion] 4.0.4.CR2 (build:
CVS
I also threw in a HttpSessionListener and validated that its sessionDestroyed
is being called for all expirations. This is with jboss running on a linux box
under jdk1.5.0_03 and the wget client running on a separate win32 box.
View the original post :
http://www.jboss.com/index.html?module=bb&
What does the tomcat stats servlet say about the app
(http://lamia:8080/status?full=true)? When I run set the jmx-console session
timeout to 1 min and run a wget loop to create a bunch of sessions:
localhost/jmx-console
Start time: Thu May 25 08:23:59 PDT 2006 Startup time: 111 ms TLD scan time
Auch, this just doesn't go away ... JBossAS 4.0.4GA
I have like 800 session that are still alive .. and the stuff is just getting
bigger:
| User Streams | Bot Streams | Both
|
| 66.249.65.36 [1 reqs][last click 0 min ago]
| 66.249.65.36 [1 reqs][last click 0 min ago]
| 66.249.65.3
Hello!
I am having exactly the same problem.
My sessions are timing out as expected when testing on WinXP but not in
production on Suse Linux 9.
/Erik
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942773#3942773
Reply to the post :
http://www.jboss.com/in
When I test this on my local machine - WinXP - the sessions are destroyed as
expected.
But when running in production on Linux - some of them are never destroyed - as
seen from my previous post.
I looked at the catalina's StandardSession (or StandardManager) code and there
is no such stuff that
Grrr, using JBossAS 4.0.4.CR2 also doesn't help.
I still get a huge number of never expired sessions:
| [7 reqs][last click 4159 min ago]
| [1 reqs][last click 2864 min ago]
| [7 reqs][last click 3128 min ago]
| ...
|
anonymous wrote :
| sessionMaxAliveTime ... 12821 ... Longest ti
4.0.1 had a problem with distributed setting breaking the session timeout, but
it was fixed in 4.0.2. Unless your using the stable 4.0.3SP1 release who knows
if it or another issue crept in.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930828#3930828
Reply
I'm having the same problem with JBossAS 4.0.3RC1 (jdk5).
I have a timeout set to 30min
|
| 30
|
|
But some of the sessions are still alive after more (way more) than 30min:
A simpe stats page layout:
| # 212.118.92.45 [1 reqs][last click 8389 min ago]
| # 193.7
11 matches
Mail list logo
