Stopping a file upload takes a lot of time

[hebe]

Hi everybody,

I have some trouble with the rich:fileupload component rather with stopping the current file upload.

First of all almost everything works perfect with this component for me and it is absolutely great.

Unfortunately I noticed some problems with stopping a running upload. It takes very long to stop the upload according to the size of the file. For very small files (a few KB) everything is ok but when the filesize is very large (round about 50 MB) it takes a few minutes (!!!) to stop the current upload.

Has anybody a solution or an explanation for this problem?
Or as a quick workaround: Is there any possibilty to disable the stop button?

(I'm using RF 3.2.2 and Seam)

My web.xml:

<filter-name>Seam Filter</filter-name>
<filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>

<init-param>
<param-name>createTempFiles</param-name>
<param-value>true</param-value>
</init-param>

<init-param>
<param-name>maxRequestSize</param-name>
<param-value>100000000</param-value>
</init-param>

My component (it is nested inside a modal panel):

<rich:fileUpload id="uploadFileComponent"
maxFilesQuantity="10"
immediateUpload="false"
fileUploadListener="#{uploadBean.uploadListener}"
listHeight="350"
listWidth="470"
autoclear="false"
>

If you need any further information don't hesitate to ask me.
Thanks in advance

[ilya_shaikovsky]

did you have any other filters defined in web.xml?

also could you please just check using laetst 3.3.0 snapshot?

[hebe]

No there are no other filters in my web.xml.

I've just tried it with the latest snapshot (from 2008-11-14) but the behavior is exactly the same.

[ilya_shaikovsky]

yes.. we've seen such behaviour but its only reproducable under local servers... And we could not influence on this.. When the speed is so high as for local connection browser tries to send data even if server stoped the request. Should be ok deployed to production servers.

[hebe]

Unfortunatly I can't confirm this behaviour. It is still the same when we deploy it to our production server. Have you any other idea about a possible solution rather what we can try?

For me it seems at the moment that we can't solve this problem within a short time. So, is there any possiblility to disable the stop button or even better is there a way to avoid the rendering of it?

Thanks for your help!

[nbelaevski]

Problem confirmed.