Closed afscrome closed 3 weeks ago
@karolz-ms Any thoughts
@karolz-ms Any thoughts
Not good. Should not happen. Will take a look.
Latest DCP insertion has several updates that should resolve this issue. First we've increased the default timeout on read/write. Second, the timeout on read and write were being set at the same time, which meant that a long read could use up most of the allowed time for a write; now we're setting the write timeout only once read is complete, meaning read and write both have the full allowed timeout to complete. I haven't been able to trigger any errors with the provided sample using the latest build.
Confirming that after upgrading to aspir e8.2, I'm now able to use the proxy. My app has now lasted for several hours dying due to a SQL failure. Thank you very much @danegsta .
Is there an existing issue for this?
Describe the bug
I have a sql query I need to run against aspire which involves sending a 184 MB file through a SQL Parameter, however this large file keeps on failing due to the network request being terminated. I'm guessing I'm hitting some kind of buffer limit which needs to be bumped up
The request goes through fine however if I bypass the aspire proxy.
Expected Behavior
The query should complete successfully.
Steps To Reproduce
Run the following powershell:
Exceptions (if any)
.NET Version info
Anything else?
If I go to the sql container w/out the aspire proxy, or disable proxying on the sql database resource, then this query succeeds w/out issue