What steps will reproduce the problem?
1. Currently uses container default (Tomcat 30 minutes) idle timeout.
2. If no session activity occurs for that length of time, an error occurs and
user and to login again.
3. For a high-risk application such as this, should be something shorter in
case the screen is left away.
What is the expected output? What do you see instead?
1. Default to something shorter (like 10 minutes) and inform administrator how
to customize in documentation.
Original issue reported on code.google.com by joshdrum...@gmail.com on 27 Dec 2010 at 12:18
Original issue reported on code.google.com by
joshdrum...@gmail.com
on 27 Dec 2010 at 12:18