If you have a web server running IDM WS, and you use server login context when connecting to the IS server, any user sessions that the Session Manager does not kill, remain active on the IS server side. Reboot your web server, and your users may be out of sessions if the limit is not set high enough.
The question is: how can you gracefully close user sessions under management by Session Manager if you need to reboot the box? Why doesn't Session Manager, when shutting down because its host process is being shut down, send a logoff request to the server for all outstanding sessions?
And for that matter, what process space does Session Manager run in? Never can get any answers from IBM or anyone else for that matter.
Source: Experience, confirmation from FileNet admin
Friday, November 6, 2009
FileNet IS server does not clean up dead sessions until recycled
Labels:
FileNet,
programming,
systems
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment