You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Matthias Keller (JIRA)" <ji...@apache.org> on 2012/10/26 08:45:12 UTC
[jira] [Created] (WICKET-4842) WicketRuntimeException when Tomcat
cleans up a session later on
Matthias Keller created WICKET-4842:
---------------------------------------
Summary: WicketRuntimeException when Tomcat cleans up a session later on
Key: WICKET-4842
URL: https://issues.apache.org/jira/browse/WICKET-4842
Project: Wicket
Issue Type: Bug
Affects Versions: 1.5.7
Reporter: Matthias Keller
When I let my tomcat 6 sit around for a couple hours, a session will expire after a while.
Exactly 4 hours after the last request, I then get this stacktrace on system out:
{quote}
[exec] 25.10.2012 19:59:08 org.apache.catalina.core.ContainerBase backgroundProcess
[exec] WARNUNG: Exception processing manager org.apache.catalina.session.StandardManager@b3f7eb background process
[exec] org.apache.wicket.WicketRuntimeException: There is no application attached to current thread ContainerBackgroundProcessor[StandardEngine[Catalina]]
[exec] at org.apache.wicket.Application.get(Application.java:231)
[exec] at org.apache.wicket.protocol.http.AbstractRequestLogger.<init>(AbstractRequestLogger.java:111)
[exec] at org.apache.wicket.protocol.http.RequestLogger.<init>(RequestLogger.java:45)
[exec] at org.apache.wicket.Application.newRequestLogger(Application.java:759)
[exec] at org.apache.wicket.Application.getRequestLogger(Application.java:439)
[exec] at org.apache.wicket.protocol.http.WebApplication.sessionUnbound(WebApplication.java:511)
[exec] at org.apache.wicket.session.HttpSessionStore$SessionBindingListener.valueUnbound(HttpSessionStore.java:454)
[exec] at org.apache.catalina.session.StandardSession.removeAttributeInternal(StandardSession.java:1654)
[exec] at org.apache.catalina.session.StandardSession.expire(StandardSession.java:756)
[exec] at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592)
[exec] at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:680)
[exec] at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:665)
[exec] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316)
[exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
[exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
[exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
[exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
[exec] at java.lang.Thread.run(Thread.java:662)
{quote}
--
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
[jira] [Resolved] (WICKET-4842) WicketRuntimeException when Tomcat
cleans up a session later on
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4842.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.9
6.3.0
Assignee: Martin Grigorov
> WicketRuntimeException when Tomcat cleans up a session later on
> ---------------------------------------------------------------
>
> Key: WICKET-4842
> URL: https://issues.apache.org/jira/browse/WICKET-4842
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.7
> Reporter: Matthias Keller
> Assignee: Martin Grigorov
> Fix For: 6.3.0, 1.5.9
>
>
> When I let my tomcat 6 sit around for a couple hours, a session will expire after a while.
> Exactly 4 hours after the last request, I then get this stacktrace on system out:
> {quote}
> [exec] 25.10.2012 19:59:08 org.apache.catalina.core.ContainerBase backgroundProcess
> [exec] WARNUNG: Exception processing manager org.apache.catalina.session.StandardManager@b3f7eb background process
> [exec] org.apache.wicket.WicketRuntimeException: There is no application attached to current thread ContainerBackgroundProcessor[StandardEngine[Catalina]]
> [exec] at org.apache.wicket.Application.get(Application.java:231)
> [exec] at org.apache.wicket.protocol.http.AbstractRequestLogger.<init>(AbstractRequestLogger.java:111)
> [exec] at org.apache.wicket.protocol.http.RequestLogger.<init>(RequestLogger.java:45)
> [exec] at org.apache.wicket.Application.newRequestLogger(Application.java:759)
> [exec] at org.apache.wicket.Application.getRequestLogger(Application.java:439)
> [exec] at org.apache.wicket.protocol.http.WebApplication.sessionUnbound(WebApplication.java:511)
> [exec] at org.apache.wicket.session.HttpSessionStore$SessionBindingListener.valueUnbound(HttpSessionStore.java:454)
> [exec] at org.apache.catalina.session.StandardSession.removeAttributeInternal(StandardSession.java:1654)
> [exec] at org.apache.catalina.session.StandardSession.expire(StandardSession.java:756)
> [exec] at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592)
> [exec] at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:680)
> [exec] at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:665)
> [exec] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316)
> [exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
> [exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
> [exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
> [exec] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
> [exec] at java.lang.Thread.run(Thread.java:662)
> {quote}
--
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