[jira] Commented: (WICKET-852) Request Cycle TimeOut

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525616 ] 

Igor Vaynberg commented on WICKET-852:
--------------------------------------

looks like this has been inactive for a while so i am resolving it as incomplete for now.

also to note, lookslike the thread is being interrupted, so it must be something outside of wicket - most likely the servlet container that is timing out what it thinks to be a runaway request thread. if this is indeed the case there is nothing we can do. you have to tweak your servlet container to also extend the timeout.

> Request Cycle TimeOut
> ---------------------
>
>                 Key: WICKET-852
>                 URL: https://issues.apache.org/jira/browse/WICKET-852
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: Application server: jetty
> OS: Kubuntu
>            Reporter: Yoshizaki Gustavo
>            Assignee: Igor Vaynberg
>
> In the init() method of the application (entends webApplication) I set:
> getRequestCycleSettings().setTimeout(Duration.ONE_HOUR );
> But always get the following error:
> 09:00:05,290 ERROR [RequestCycle] java.lang.InterruptedException
> wicket.WicketRuntimeException: java.lang.InterruptedException
>     at wicket.Session.getPage(Session.java:431)
> This is an error thrown in Session.class:
> try
> {
>       pageMapsUsedInRequest.wait(timeout.getMilliseconds());
> }
> catch (InterruptedException ex)
> {
>       throw new WicketRuntimeException(ex);
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.