Unused active sessions are not getting timed out

Hi experts,

I have a setting where client_session_timeout is 5 minutes (default). But under some circumstances (dont know what), unused sessions remain active for long period of time (say 8 hours) which causes max session exceeded.

I find that unused sessions are active by executing "list_sessions" query in which "last_used" time shows sessions are not been used for more than 8 hours. Please help me know why the sessions are not timed out after 5 minutes of inactivty.

Most of the sessions are establised by custom WDK application where i use session manager to establish and release sessions. Normally the sessions are getting timed out correclt (after 5 mins of inactivity). But suddenly the issue occurs. Please share your ideas on this.

Few details:

DCTM 6.5 (upgraded)

max session =400

client sess timeout =5

history cutoff =60

Find more posts tagged with

Documentum

Comments

CristianOrellana

Hello,

Check the following:

http://www.xense.co.uk/resources_dctm_sessions.htm

It will help you a lot.

Regards.

agboan

LIST_SESSION tells you the machine of origination of the connection - and the type of authentication.

Do you see any common thing - that active sessions have some common machine of origination?

prabhu

API>dumpconnectpool is working in 5.3 but its not working in 6.5 . list_sessions lists only the server side sessions. Is there a way to see the client side sessions ??

Francois Dauberlieu

Probably talking bull... here but it could also be, if you use Webtop that your http sessions stay forever and if your app server is configured with a sort of keep alive, it will also keep the Documentum sessions.

On you app server, try to kill a few sessions and wait for the 5-6mn to see if the Documentum sessions are timed out too

My 2 cents