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

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5985.
-------------------------------------
    Resolution: Won't Fix

This is fixed long time ago in Wicket 7.x.
Wicket 6.x cannot use Servlet 3.x APIs so this check cannot be done (unless using Reflection APIs).

You are recommended to upgrade to Wicket 7.0.0+

> 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)