Communications Express and session-timeout
I'm not sure if asking a question about session-timeout is appropriate on the Messaging server forum, if it's not, please direct me to the proper forum.
Our users have been complaining of being timed out on a Communications Express (CE) while their session is still active. By that I mean they could be typing a message and their session will time out.
I found the setting in /var/opt/SUNWuwc/WEB-INF/web.xml:
<session-timeout>600</session-timeout>
or ten minutes.
Any explanation why active session are being timed out or any other values I should check?
Thanks
-- Bob
[633 byte] By [
rkbunca] at [2007-11-26 11:58:17]
# 1
> I'm not sure if asking a question about
> session-timeout is appropriate on the Messaging
> server forum, if it's not, please direct me to the
> proper forum.
>
> Our users have been complaining of being timed out on
> a Communications Express (CE) while their session is
> still active. By that I mean they could be typing a
> message and their session will time out.
>
> I found the setting in
> /var/opt/SUNWuwc/WEB-INF/web.xml:
>
> <session-timeout>600</session-timeout>
>
> or ten minutes.
>
> Any explanation why active session are being timed
> out or any other values I should check?
>
> Thanks
>
> -- Bob
Please check:
http://forum.sun.com/jive/thread.jspa?forumID=15&threadID=48724
Ram
# 2
Ram,
Thanks for your speedy response. Here are the timeout values from configutil:
service.http.idletimeout = 600
service.http.resourcetimeout = 900
service.http.sessiontimeout = 7200
From the forum post you referenced it looks likke the idletimeout values is for 600 minutes or 10 hours. This doesn't explain why our users are being timedout when active?
Any ideas?
# 3
Are you using Access Manager? and UWC?
If this is correct please do...
The correct answer is...
Log into your Sun Java System Identity Server... go to the Service Configuration tab... select Session... then in the right-hand window set your desired Maximum Session Time and Maximum Idle Time in minutes. I picked 600 minutes (10 hours) and 480 minutes (8 hours). I may bring these numbers down later if resources become an issue.
You can review this by selecting the Current Sessions tab to see who's logged in and with what timeouts. No service restart is necessary. So... UWC timeouts are controlled by the Identity Server.
Ram
# 4
If you would provide the version information we always ask for, I might be able to offer you a patch.There was a recent patch for the Access Manager, which broke the UWC session. The symptoms are as you describe.Getting the latest Messaging patch and UWC patch will fix it.
# 5
Hi Jay,Thanks for your suggestion, and hope a patch is available.I'm not sure exactly how to get the versions you need to determine if we are at the correct maintenance level. When I run amadmin --version I see:Sun Java System Access Manager 7 2005Q4
# 6
Best way to get a Messaging Server version:imsimta versionthe patch (assuming sparc) 118207-58 messaging core,118540-21 UWC
# 7
# ./imsimta version
SunOS uwc 5.10 Generic_118833-18 sun4u sparc SUNW,Sun-Fire-V240
Sun Java(tm) System Messaging Server 6.2-6.01 (built Apr 3 2006)
libimta.so 6.2-6.01 (built 11:20:35, Apr 3 2006)
It looks like we are running with the following levels of those patches:
Patch: 118207-38 Obsoletes: 116800-06, 116568-99, 117781-01, 118002-02 Requires: Incompatibles: Packages: SUNWmsgin, SUNWmsgen, SUNWmsglb, SUNWmsgco, SUNWmsgmt, SUNWmsgst, SUNWmsgmp, SUNWmsgwm, SUNWmsgmf
and
Patch: 118540-37 Obsoletes: 117287-99, 117819-13, 119156-07 Requires: Incompatibles: Packages: SUNWuwc
# 8
Yes. You should be upgrading to 118207-58. It's on sunsolve, released.
# 9
I started downloading it as soon as I got your message.Thanks...I'll post the results after it's applied.
# 10
Hi Jay,
Just checked and found that we are running 118207-51, on the server which runs Communications Express. The server I mentioned in my previous message is running our calendaring and messaging servers. I'm assuming that both of the servers should be running the same version of the patch, right?
Also I searched the README for 118207 and there are a lot of bugids that mention timeout. I was curious which bugid references the problem we are experiencing? It's not obvious from the often terse bug description.
Thanks.
# 11
Hi Jay,
Just checked and found that we are running 118207-51, on the server which runs Communications Express. The server I mentioned in my previous message is running our calendaring and messaging servers. I'm assuming that both of the servers should be running the same version of the patch, right?
Also I searched the README for 118207 and there are a lot of bugids that mention timeout. I was curious which bugid references the problem we are experiencing? It's not obvious from the often terse bug description.
Thanks.
# 12
Hi,
The biggest cause of customer timeout issues was:
6442580 XFILE 6436876: UWC session timeouts using latest AMSDK 7.0
This is most likely the issue you are hitting. It is usually best to keep servers at even patch releases especially if there are fixes which have interdependent changes e.g. having to upgrade calendar server to satisfy a CE or Outlook Connector bug.
Regards,
Shane.
