Session Timeout After Half An Hour While Uploading Files To Content Server Using CWS

Greetings,

I'm trying to upload a descent amount of files to the Content Server using CWS.
Somewhere around 30 min of processing, I'm getting a timeout exception stating that the session has expired.
Since it's a great amount of files it'll take time to transfer them and it'll take more than half an hour.

Is there a way to increase the timeout buffer? If so, what is the maximum size that can be reached?

Thanks.

Find more posts tagged with

Comments

Appu Nair

The cookie settings of a CS is what governs what the time is you get to it from here see screencap.
?func=admin.securityvars

https://knowledge.opentext.com/knowledge/cs.dll/Properties/77914423

Another thing frequently programmers do is to look at your authentication token and ask if you are valid and re-fetch it. REST API impl by OT with each successive calls returns you the token so you can conveniently chain it even if
you are hitting an LB.In CWS LB it is imperative that you hit the same machine or relax settings of the above setting.

Greg Griffiths

I would be wary of just upping the timeout values as this will apply to all events on the server, you would be better off using the check token approach that @Appu Nair suggests

Shai Abadi

Changing settings at : ?func=admin.securityvars did solve the issue but another time out has appeared.

It seems that this time out concerns app.config settings and DocumentManagement.svc. This is how my app.config file looks like :

Image: https://us.v-cdn.net/6030023/uploads/editor/mj/bteldywx2afh.png

I did try to change the values for a longer period but without any success. I'm not sure even if those changes affect something.
I'd appreciate any advice or if someone here encounter this kind of problem and might assist me resolve this.

Appu Nair

if I remember correctly you have to change timeouts on the Web.Config if it is IIS or corresponding file in Tomcat if CWS runs in that container. Then if it is client code you have to refresh that. At that point what the server holds will be transferred to client. The XML you are showing is WCF properties and not OT property. You can go to any google page and look for that stuff's meaning and follow that.Some of us when we were active would have posted examples as well. But essentially there is what one calls DOS attacks which can happen if you keep sockets open longer than they are needed. More a socket remains open more it is taxing to the application(Memory Leaks). This is why OT has given a simple command to test if your AuthToken is about to expire.Good programmers should use that provision.

in VSS after I change it on Web. Config there is a button that you push in your project to get the refreshed app.config that is what I meant.If that means you have to rebuild your application sometimes it needs to. Most of my C# CWS I have tried to o use its Application. Config which it throws in the debug or release folder of .net.If you edit that to your server things many times it should work with the revised settings and not necessitate the application rebuild.

Once again I ask you to not change things to kill the system