[#JRA-14311] Ability to configure a persistant session timeout

JIRA

Ability to configure a persistant session timeout

Created: 18/Jan/08 01:28 PM Updated: 20/Jan/08 04:38 PM

Component/s:

Administration

Affects Version/s:

3.12.1

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

war deployment

Participants:	Dmitry Beransky and Dylan Etkin [Atlassian]
Since last comment:	31 weeks, 3 days ago
Labels:	session administration

Description

« Hide

Currently the only way to configure a session is by modifying the web.xml file. The major shortcoming of this approach is that the change is transient. Web.xml gets overwritten every time the war file is rebuild or Jira is upgraded. The session timeout value must be configurable via the administrative interface and must be persisted in the database.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 20/Jan/08 04:15 PM - edited

Hi Dmitry,

I am afraid that this is an application container specific setting and not something that we can control from the JIRA application. When the JIRA application is brought up in the container this setting has already been configured. I don't think there is really much we can do about this. Do you think we can close this issue?

Thanks,
Dylan

[ Permlink | « Hide ]

Dmitry Beransky added a comment - 20/Jan/08 04:38 PM

Yes you can. I''ve done exactly that with my applications. You register a session listener and whenever a session is created, set its timeout value.

http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#setMaxInactiveInterval(int)