Hi, I found the solution. Yes, I have a failure callback listener, and it is actually invoked. The question was why this happens, i.e. why the Ajax response is not received by the client, as if it lost connection with the server. The answer is related to Tomcat: in fact the maximum size for aborted uploads that Tomcat is configured to "swallow" is 2MB. Nonetheless, it is possible to configure the Connector by setting the attribute maxSwallowSize. Thanks to you. Best -- Marco
On 30 May 2017 at 20:45, Martin Grigorov <mgrigo...@apache.org> wrote: > Hi, > > Do you have a failure callback listener for this Ajax call ? > See IAjaxCallListener#onFailure(). > If this doesn't help then please create a quickstart application and attach > it to a ticket in JIRA! > Thanks! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Tue, May 30, 2017 at 5:39 PM, marco di gasbarro <m.digasba...@gmail.com > > > wrote: > > > Hi there, > > I am struggling with this issue using Tomcat 8.5.14 and Wicket 6.24 > > > > When FileUploadBase$FileItemIteratorImpl constructor throws > > SizeLimitExceededException, the ajax response is not read by the browser > > client, which keeps waiting (Firefox) or aborts (IE) the connection, with > > the following ajax error: > > "Cannot read Ajax response for multipart form submit: TypeError: > Permission > > denied > > Wicket.Ajax.Call.failure: Error while parsing response: No XML response > in > > the IFrame document" > > > > Thank you > > -- > > Marco > > >
