Hi Dragos, I see. I think you can configure the lifetime of the cookie. you might want to look for Form Based Authentication configuration in the Web Console Configuration page.
But "1984720ms ago" sounds like more than half an hour. This is quite a large upload ? Or a terribly slow network connection ? Regards Felix Am 04.09.2012 um 13:32 schrieb Dascalita Dragos: > Thanks for your help Felix. > > In the error.log I get these lines, when upload starts and when upload > completes: > > 04.09.2012 *00:34:17.411* *INFO* [764032934@qtp-1811226204-1067] > logs/request.log 04/Sep/2012:00:34:17 +0200 [66449] -> > *POST*/content/channel/adventist_at/vod/2012/9/Test%20large%20video > HTTP/1.1 > ... > 04.09.2012 *01:24:00.647* *ERROR* [805807454@qtp-1811226204-1071] > org.apache.sling.auth.form.impl.TokenStore AuthNCookie value > 'fd123188d4058cba49a1af74258fa2d8b3c37a3e@21346712655926@daniel' *has > expired 1984720ms ago* > 04.09.2012 01:24:00.647 *INFO* [805807454@qtp-1811226204-1071] > org.apache.sling.auth.core.impl.SlingAuthenticator handleLoginFailure: > Unable to authenticate daniel: null > 04.09.2012 01:24:00.647 *INFO* [805807454@qtp-1811226204-1071] > org.apache.sling.auth.core.impl.SlingAuthenticator login: No handler for > request (3 handlers available) > 04.09.2012 01:24:00.647 *ERROR* [805807454@qtp-1811226204-1071] > org.apache.sling.auth.core.impl.SlingAuthenticator doLogin: Cannot login: > No AuthenticationHandler available to handle the request > 04.09.2012 01:24:00.647 *INFO* [805807454@qtp-1811226204-1071] > logs/request.log 04/Sep/2012:01:24:00 +0200 [66502] <- 403 text/plain > 2926740ms > > > Thanks, > Dragos Dascalita Haut > > On Tue, Sep 4, 2012 at 10:11 PM, Felix Meschberger <[email protected]>wrote: > >> Hi, >> >> Am 04.09.2012 um 13:06 schrieb Dascalita Dragos: >> >>> Hi, >>> I'm having this issue that during long file uploads, by the time upload >>> completes, the session expires and users can't save data into JCR. >>> I tried calling an URL [1] from time to time during uploads, to try >> keeping >>> the session active, but even with that, the session still expires. >>> >>> What would be the best way to keep the session active during uploads ? >> >> Each request has its own session. The session is created when request >> processing starts and logged out at the end of processing. >> >> So, if your upload takes a long time, there may be other time outs taking >> place than the session timing out. In addition IIRC a JCR session actually >> never times out. >> >> Or are you talking about an HTTP Session ? >> >> Regards >> Felix
