This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
George,
Tell us a bit more about why you think this is a problem? We "suffer"
from this also. Maximo 6.2.4, Weblogic, Oracle. But I've been keeping
a close eye on active and inactive sessions as recorded in maxsession,
and can see that inactive sessions are reliably killed after 30
minutes. We are peaking at up to 60 total sessions for a few minutes
each morning, but system remains stable.
We do periodically remind users that failing to log off can cause
performance issues. Maybe ours are better at listening than yours are,
but that remains to be proven.
Jake in Walla Walla
We have it also to where after 30 mins it expires and triggers the log off
function. But I'm seeing that some are not being killed after the time
limit.
I'm just finding out that some user's didn't even know there was a log out
function. The person before me in charge of maximo didn't do much training
the users.
And like you said it can cause performance issues but to what extent and
how many users does it take before you start see the issues?
We have alot of issues here with maximo that I'm trying to figure out, and
have had no training. I've come along way in a short time.
Just tackling one issue at a time.
Thank You,
George Gutierrez Jr.
Maximo Administration
Pasadena Refining Systems
713.920.3908 Direct
832.473.5330 Cell
U1O2 - Chave
From: Jake <jsteijn@gmail.com>
To: MAXIMO@yahoogroups.com
Date: 08/31/2012 12:14 PM
Subject: [MAXIMO List] Re: Users closing browser window and logging out
Sent by: MAXIMO@yahoogroups.com
George,
Tell us a bit more about why you think this is a problem? We "suffer"
from this also. Maximo 6.2.4, Weblogic, Oracle. But I've been keeping
a close eye on active and inactive sessions as recorded in maxsession,
and can see that inactive sessions are reliably killed after 30
minutes. We are peaking at up to 60 total sessions for a few minutes
each morning, but system remains stable.
We do periodically remind users that failing to log off can cause
performance issues. Maybe ours are better at listening than yours are,
but that remains to be proven.
Jake in Walla Walla
I can reliably kill Maximo by hitting it with 52 logins in a 5 minute window. It will hang and I have to kill the java process to even restart it. Again, this is on Windows 2003 32 bit, 1 GB heap JVM. I think the rapidfire login activity "helps" it choke itself on resource requests. There is a recognized bug that is reputed to affect Maximo 6 which causes the stale session killer to fail. I have not installed it, because I cannot detect incidents of this type. The fix is included in 6.2.8, or you can ask for the hotfix if you dare.APAR # IZ96123 Issue 11-12117.
--- In MAXIMO@yahoogroups.com, ggutierrez@... wrote:
>
> We have it also to where after 30 mins it expires and triggers the log off
> function. But I'm seeing that some are not being killed after the time
> limit.
Jake in Walla Walla