[
https://issues.apache.org/jira/browse/WICKET-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587645#action_12587645
]
Johan Compagner commented on WICKET-1478:
-----------------------------------------
Also the discussion there is about session leakage and so on on the mailing list
i also did get some mails where people where checking
Application/Session/RequestCycle and RequestContext
if they where still there at points (complete beginning of a request)
And they told me that RequestContext was still there quite a lot.. So that
seems wrong somehow i am also investigation that some more
But if you could check for places where the RequestContext is not cleared (and
application and session are) ...
> AbortWithWebErrorCodeException in onBeforeRender causes WicketRuntimeException
> ------------------------------------------------------------------------------
>
> Key: WICKET-1478
> URL: https://issues.apache.org/jira/browse/WICKET-1478
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2
> Reporter: Michael Sparer
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 1.3.4
>
> Attachments: quickstart404.jar
>
>
> Using custom error pages as described on
> http://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html, a
> wicket RTE gets thrown "There is no application attached to current thread
> [threadname]" when a AbortWithWebErrorCodeException is thrown in the
> onBeforeRender method of a WebPage. Note that this _only_ happens when using
> a custom error page defined in web.xml.
> See attached quickstart for the complete stacktrace (and my usecase)
> See also the mailinglist entry on
> http://www.nabble.com/Throw-AbortWithWebErrorCodeException-in-onBeforeRender-to16446341.html#a16473849
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
