[jira] [Commented] (WICKET-5985) WritePendingException when serving static assets from Jetty with Wicket

["Jeremy Sss (JIRA)" <ji...@apache.org>]

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

Jeremy Sss commented on WICKET-5985:
------------------------------------

Thanks [~martin-g]. I thought for sure that I tested with Wicket 7.x and saw the same error but I must have failed to clean my project before building because I just retested and everything is looking fine. Does setAsyncSupported(false) have any other side-effects that you know of assuming I stick with Wicket 6.20.0 for a while before upgrading?

> WritePendingException when serving static assets from Jetty with Wicket
> -----------------------------------------------------------------------
>
>                 Key: WICKET-5985
>                 URL: https://issues.apache.org/jira/browse/WICKET-5985
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.20.0
>         Environment: Windows 7 x64
>            Reporter: Jeremy Sss
>            Priority: Minor
>
> I posted a bug report on Jetty's bug tracker recently about some WritePendingExceptions I was getting when I requested static content (external issue url attached). Jetty is serving that static content asynchronously (to save threads), so the WicketFilter should not be calling flushBuffers as it is. The Jetty team suggested that the WicketFilter be updated to understand that content can be created asynchronously.
> A workaround in the meantime is that I can set the WicketFilter to be installed as not supporting async: 
> wicketHolder.setAsyncSupported(false);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)