Support forums
in

Failed on ReadEntityBody, unexpected data ending

Last post 10-26-2010, 3:34 AM by dyte. 7 replies.
Sort Posts: Previous Next
  •  10-12-2010, 2:51 AM 64404

    Failed on ReadEntityBody, unexpected data ending

    Hello:
     
    A customer reported the following error.
    The upload - consisting of a 250 MB file - had been going well for 45% percent, then an alert window appeared saying: 
     
    Flash: The upload task is interrupted! io Error #2038
    Server side error: System.Exception: Error:Failed on
    ReadEntityBody, unexpected data ending (2)
    261544932/580366736
     at CuteWebUI.a.a(HttpContext A_0,
    HttpWorkerRequest A_1, MemoryStream A_2, FileStream
    A_3, String& A_4)
     at CuteWebUI.a.b(HttpWorkerRequest A_0)
     at CuteWebUI.UploadModule.d(HttpContext A_0)
     
    He uses Mac OS, and Firefox 3.6.  (it happened again after retrying)
    Any ideas about the cause of this and the solution?
  •  10-12-2010, 4:14 AM 64405 in reply to 64404

    Re: Failed on ReadEntityBody, unexpected data ending

    Hi,
     
    When uploader throws this error, it means the server did not get any data from client side for 12 seconds.
     
    Maybe the customer will also see the progress have stopped for 12 seconds before the alert be shown.
     
    Network problem can cause this issue.
     
    If your customer can always get such problem,
     
    You can test this appSettings in web.confg:
     
    <add key="CuteWebUI..AjaxUploader.UseAspNetStream" value="True" />
     
    Regards,
    Terry
  •  10-12-2010, 8:29 AM 64406 in reply to 64405

    Re: Failed on ReadEntityBody, unexpected data ending

    Interesting.
    What exactly will this setting do?
    Thanks for getting back .
     
    Dieter
  •  10-12-2010, 8:39 AM 64407 in reply to 64405

    Re: Failed on ReadEntityBody, unexpected data ending

    Another thing, my boss just asks me the following:
     
    Is it possible, when the connection is lost, that the uploader will retry a few times, preserving the bytes already uploaded, so when the connection is reestablished, the upload will continue at the same point, similar to how FTP works.
     
    Is there a similar mechanism available within ajaxuploader?
  •  10-17-2010, 8:17 PM 64457 in reply to 64407

    Re: Failed on ReadEntityBody, unexpected data ending

    Hi,
     
    The newest version which was released yestoday now support this feature.
     
    Please download it and try again.
     
     
    For silverlight it will try to resume the uploading automatically.
     
    For Flash mode , you need set the FlashLoadMode to true , but this is not good for large files.
     
     
    So, for big files, I suggest you use UploadType=Silverlight
     
     
    Regards,
    Terry
     
  •  10-18-2010, 10:47 AM 64474 in reply to 64457

    Re: Failed on ReadEntityBody, unexpected data ending

    That sounds very interesting.
     
    Two questions: Why exactly is FlashLoadMode set to true bad for large files?
     
    And second, is there a  timeout value that we can customize, of how long an interruption can maximum be, for ajaxuploader still be able to resubmit the data?
     
    Thank you.
  •  10-19-2010, 8:49 PM 64509 in reply to 64474

    Re: Failed on ReadEntityBody, unexpected data ending

    Hi,
     
    Silverlight can read small chunk of data from the file
     
    But Flash only support read all file data into memory.
     
    So if use Flash mode to open a 500MB file , 500MB data will read to memory , and the browser will hang for a while.
     
    Now we do not provide timeout setting . the auto logic is ,
     
    If the file is transfered for 10 minutes , the uploader will try to resume at lease 5 minutes.
     
    User can cancel the current file if he see the progress is stopped and do not want to wait.
     
    Regards,
    Terry
  •  10-26-2010, 3:34 AM 64692 in reply to 64509

    Re: Failed on ReadEntityBody, unexpected data ending

    I see.
     
    We installed the latest version and tested both silverlight and flash. As you predicted, flash was terrible with large files and the setting flashloadmode set to true.
    Silverlight seemed to do a bit better,but still had big delays, and wasn't able to finish, showing the following error in an alert window:
     
    SLM error:Error:Target length is bigger then file size!
     
    Any idea what this error is about?
View as RSS news feed in XML
Powered by Community Server (Commercial Edition), by Telligent Systems