Hello,
>
> Hi Mathijs,
>
> I think cocoon.session maps to the HTTPSession object.
> HTTP session TTL is managed by the servlet container (Tomcat
> for example). Default session timeout value for Tomcat is 30 minutes.
correct AFAIK
> But if you use continuations, beware that as far as I know, a
> continuation also has a timeout value of 10 minutes, I think
> (someone please correct me).
continuation ttl is configurable in cocoon.xconf
<!--+
| Configuration for the continuations manager.
|
| This section specifies the default time-to-live of continuations
| in miliseconds using the "time-to-live" attribute of
| the <continuations-manager> element.
|
| The <expirations-check> element specifies different policies for
| expiring continuations. Currently only the "periodic" type is
| supported.
+-->
<continuations-manager logger="flow" time-to-live="3600000">
<expirations-check type="periodic">
<offset>180000</offset>
<period>180000</period>
</expirations-check>
</continuations-manager>
>
> PS : Hippo gurus are gone in holidays :) ?
No....just incredibly busy :-)
Ard
>
> HTH,
> --
> Olivier Billard
>
>
>
> Mathijs Brand wrote:
> > Hello,
> >
> > Does anyone know what the default cocoon.session keep alive time is?
> >
> > Met vriendelijke groet,
> > Mathijs Brand
> > Hippo
> > Oosteinde 11
> > 1017WT
> > Amsterdam
> > The Netherlands
> > Telefoon: +31(0)20-5224466
> > Fax: +31(0)20-5224467
> > -------------------------------------------------------------
> > [EMAIL PROTECTED] / www.hippo.nl
> > --------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
