nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to increase session time out for content workspace

Vikaas_Neekhra

We are facing some session timed out issue while updating any content and all of a sudden content workspace logged off and then we lost our data. So if we can increase the time out should help in this issue, we are using below version. And if anyone can help us on how to increase the time out would be much appreciated.

Version: Web Experience Management 8.5 SP1+Cumulative

Thanks!

Find more posts tagged with

Comments

Doug_McLaren

We have a perl script that we've given out to customers that looks for web.xml files -- either in a deployed webapp, or inside of a ear or war -- and updates the <session-timeout> variable -- and I believe it will do what you need.

I don't see a way to attach it to the discussion here, so I'll email you a copy. If anybody else needs a copy, they can email me, or just open a ticket with support and request it. (The name of the script is session-timeout-changer and it was written by me back in 2008, that'll help the support engineer know what you're asking for.)

Qutubuddin

Vikas,

Are you sure that you are truly hitting a session timeout?

In past I have seen similar issue caused due to incorrect load balancing setup for preview / vcm combination. Specially, when you have got 2 load balanced preview servers backed by 2 load balanced VCM instances.

Thanks & Regards

Qutubuddin Saifuddin

Architect
Open Text
Mobile : 732 397 7951
Email : qsaifudd@opentext.com
Website : www.opentext.com

From: eLink Entry: Discussion Group - Web Experience Management [v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, October 24, 2014 2:53 PM
To: eLink Recipient
Subject: How to increase session time out for content workspace

How to increase session time out for content workspace

Posted by vikas.neekhra@xcelenergy.com (Neekhra, Vikas) On 10/24/2014 02:49 PM

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Vikaas_Neekhra

Yes, we are facing session timeout issue.

It is working now after updating the session-timeout value to 120 in below war files, but in IE browser the session remains till 120 mins.(if we do anything or not in content workspace) as we are on 121 minute then we are redirected to login screen, but ideally if the session is active (means we are still doing something in content workspace) then it should extend the session by 120 mins. What do you think?

Also in Mozilla firefox browser still the session is active till 30 mins. only, not 120 mins. as it is working in IE browser for atleast 120 mins.

cps.war, vcm-api.war and vcm-ui.war

Thanks for all the responses!

Doug_McLaren

I would not expect anything regarding the session timeout to vary from browser to browser.

There's usually not any downside to setting the timeout to last days rather than minutes -- each session does use a small amount of resources until it's timed out, but the amount is small and most servers can handle it easily.

The only exception to that that I've seen is when customers are writing programs that talk to the application server and log in each time (creating a new session) rather than keeping their cookies across invocations and that can end up creating a new session each minute or more -- that can result in a problem with a large timeout.

In any event, if changing the session timeout only works on some browsers, I'd suggest bringing that up in a ticket with support so we can look into it further. The most likely problem that I can think of would be that not all wars/ears were updated properly -- the script finds them all, but if it's done manually sometimes things are missed.