Skip to main content

[webtier] Re: Webcontainer Session Timeout - Default Value?

1 reply [Last post]
Anonymous

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Jan Luehe

Hi June,

On 01/27/09 10:33, June.Parks@Sun.COM wrote:
> On 01/27/09 10:23, Jan Luehe wrote:
>> Hi June,
>>
>> On 01/27/09 10:10, June.Parks@Sun.COM wrote:
>>> We don't document web.xml in the app server docs because it's
>>> Java-EE-generic and not app-server-specific. I mention the web.xml
>>> default only because the sun-web.xml default overrides it.
>> I agree that we normally do not have to document web.xml defaults,
>> since they are Java-EE-generic in most cases.
>>
>> However, session-timeout is an exception. The web.xml schema describes
>> it as follows:
>>
>> If the timeout is 0 or less, the container ensures
>> the default behaviour of sessions is never to time
>> out. If this element is not specified, the container
>> must set its default timeout period.
>>
>> So in the case of session-timeout, the default is app-server specific,
>> which is why I think we should document it.
> So if the web.xml session-timeout is not specified, the App Server
> sets it.
Yes.
> If the web.xml session-timeout is set but the sun-web.xml session
> timeout is not set, the web.xml session-timeout applies.

Correct.

> If both web.xml and sun-web.xml session-timeout values are set, the
> latter overrides the former. Wow, that's convoluted.

Actually, if both are specified, the web.xml takes precedence (I just
checked the code, and
confirmed that this is also how it's documented in the Deployment Guide).

I never understood the motivation for specifying the session timeout in
2 places. I would have thought
that specifying it in web.xml should be sufficient. May only explanation
would be that earlier
versions of web.xml may not have provided any configuration support for
session timeout, which
is why it was added to sun-web.xml. When it was finally added to
web.xml, support for it in
sun-web.xml had to be preserved for backward compatibility reasons.
What's further complicating
the matter is that the timeout in sun-web.xml is specified in seconds,
whereas the one in web.xml
is specified in minutes.

>
> I'm not sure I can document the web.xml session-timeout as such, but I
> can expand the sun-web.xml session-timeout explanation and make sure
> there is a good index entry or two for the web.xml session-timeout.

Great! Thanks!

I think you could rephrase what you currently have:

If neither session-timeout nor timeoutSeconds is specified, the
timeoutSeconds default is used.

to read:

If neither session-timeout nor timeoutSeconds is specified, the
session-timeout default (30 minutes),
which is the same as the timeoutSeconds default, is used.

Jan

>
> June
>>
>>
>> Jan
>>
>>>
>>> June
>>>
>>> On 01/27/09 10:04, Jan Luehe wrote:
>>>> On 01/26/09 06:24, glassfish@javadesktop.org wrote:
>>>>> Thank you, Jan;
>>>>>
>>>>> But how/where is this configured/described? Say if i want to set
>>>>> it to 60 minutes to all webappliations deployed, how to do that?
>>>>
>>>> The default session timeout (30 minutes) is documented in the
>>>> GlassFish
>>>> Developer Guide, see
>>>> http://docs.sun.com/app/docs/doc/820-4502/beaxr?l=en&a=view
>>>>
>>>> Currently, it is documented "indirectly", via the "timeoutSeconds"
>>>> session property in sun-web.xml. I could not find any documentation of
>>>> the default in web.xml, but I may not have looked in
>>>> all places. Cc'ing June.
>>>>
>>>> If you wanted to change the default session timeout to 60 minutes
>>>> and have
>>>> it take effect for all webapps, I suggest you add a session-config
>>>> element to
>>>> the domain's default-web.xml, as follows:
>>>>
>>>>
>>>> 60
>>>>

>>>>
>>>> Let me know if you have any questions about this approach.
>>>>
>>>> Thanks,
>>>>
>>>> Jan
>>>>
>>>>> Ivo
>>>>> [Message sent by forum member 'jdrive' (jdrive)]
>>>>>
>>>>> http://forums.java.net/jive/thread.jspa?messageID=328165
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>>>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: webtier-help@glassfish.dev.java.net