[
https://issues.apache.org/jira/browse/WICKET-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498254#comment-13498254
]
Byron Palmer commented on WICKET-4866:
--------------------------------------
Sorry that you closed this as it is an issue for me. I don't use Maven because
it does not work with what I need to do with libraries and it adds more
complexities than it solves. So I can't send you a quickstart example.
What I do know is that this worked up to the 1.5.7 version. When I upgraded to
the 1.5.9 or the 6.2 version the timeout went to five minutes. I do not access
the HTTPSession and modify it in any way. My best guess is that this is tied to
the dbcp pooling as that is how I get the database connections. That seems to
be set to around five minutes and am wondering if that is somehow triggering
the session close.
I tried this in both Tomcat and Jetty and got the same results. My application
is not that complicated but it has to have a database connection and is
restricted to those that login to the site. I got around the problem by taking
a common component and adding an Ajax action that keeps the session alive. I
then use a count down in the session itself and use the Ajax action to
decrement the timer and to inform the client how many minutes remain. I then
managed to have each action on the site refresh the timer so that it is
accurate. All of this adds more complexity but it got me around the issue.
I like Wicket because it solves many of the problems and makes development
easy. This last one really threw me as I didn't do anything to cause the
change. I don't know anything else to help you work on this but keep it in the
back of your mind that it could still be a problem. If you have any suggestions
as to how I could figure out what is going on I would be appreciative.
> servlet <session-timeout> ignored
> ---------------------------------
>
> Key: WICKET-4866
> URL: https://issues.apache.org/jira/browse/WICKET-4866
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.2.0, 1.5.9
> Environment: Tomcat and Jetty
> Reporter: Byron Palmer
> Labels: configuration
>
> Using the servlet configuration parameter <session-timeout> and setting it to
> larger than 5 minutes fails to work. The session is timing out before five
> minutes are up. This is a major problem as my users need to be able to work
> on a page for longer than 5 minutes.
> I have had to make my own session timer and Ajax requests to keep the session
> alive in order to make my site work. This used to work but after upgrading to
> 1.5.7 and later it has not worked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
