Hi,

I have DMX installed and working well for files up to 100Mb but when I try to upload a file of 180Mb to S3, the system never succeed and the file remains in the upload directory.
This is not a naming problem of the file (I check it). I put the the following value in web.config:



I found the following error in log:

The write operation failed, see inner exception.

Affirma.ThreeSharp.ThreeSharpException: The write operation failed, see inner exception. ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Net.UnsafeNclNativeMethods.OSSOCK.send(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags) at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode) at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) --- End of inner exception stack trace --- at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state) at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size) at Affirma.ThreeSharp.Query.ThreeSharpQuery.GenerateAndSendHttpWebRequest(Request request) at Affirma.ThreeSharp.Query.ThreeSharpQuery.Invoke[T](Request request) --- End of inner exception stack trace --- at Affirma.ThreeSharp.Query.ThreeSharpQuery.Invoke[T](Request request) at Bring2mind.DNN.Modules.DMX.Services.Storage.S3StorageProvider.S3StorageProvider.StoreFile(Int32 PortalId, String FilePath, String OriginalFilename, Boolean MoveFile)

Is it possible to tune it?
Does anybody test S3 for large files like this?

Thanks for your help,
Dom

Missing text:
httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="768000" requestLengthDiskThreshold="768000" executionTimeout="1800"

The key phrase in the error is "Thread was being aborted". This indicates IIS shut down processing. The timeout is specified in the web.config (as you've identified quite rightly in the second post) and can be accessed through the web.config config screen in DMX as well. The time needs to cover the time that your largest upload might take from the server to S3. Apparently half an hour is still not good. That is slightly worrying because it becomes pretty impractical to wait that long. Is there any way to time what is happening? Is it really taking that long to upload?

Note this is not a property of the software. DMX is subject to the same regime as all of asp.net. IIS shuts it down to protect the server from processes that have gone haywire or DOS attacks.

Peter

I found a solution...
As I see that the upload speed to S3 on my server was limited for an unknown reason to 100Kb/m, I put a larger value (2500 instead of 1800) and it works...