Hi,
I don't know if this could help, but I have the same issues with my code.
Nevertheless, I noticed something very strange while testing : my problems are related to the machine I test my code on.
I have 6 machines : 2 windows 2012 R2 Datacenter, 1 windows 2008 R2 Enterprise, 1 windows 2008 R2 standard, 1 ubuntu 14.04 (running different VMs) and 1 windows 8.1.
Thing is, the "stall" effect occurs only on my 2 machines running windows 2012 R2 Datacenter.
As all machines are physically in different places, I already excluded physical network issues by different tests and analysis (for instance, the ubuntu machine is on the same network as the machines causing problems).
I also tested the streaming API using curl, and I have issues on the same machines (curl closing connection with a "transfer closed with outstanding read data remaining" message).
I'm starting to run out of hypothesis there... Could it be a default network configuration issue like a limit on tcp packets or a too short timeout ?
I don't know if this could help, but I have the same issues with my code.
Nevertheless, I noticed something very strange while testing : my problems are related to the machine I test my code on.
I have 6 machines : 2 windows 2012 R2 Datacenter, 1 windows 2008 R2 Enterprise, 1 windows 2008 R2 standard, 1 ubuntu 14.04 (running different VMs) and 1 windows 8.1.
Thing is, the "stall" effect occurs only on my 2 machines running windows 2012 R2 Datacenter.
As all machines are physically in different places, I already excluded physical network issues by different tests and analysis (for instance, the ubuntu machine is on the same network as the machines causing problems).
I also tested the streaming API using curl, and I have issues on the same machines (curl closing connection with a "transfer closed with outstanding read data remaining" message).
I'm starting to run out of hypothesis there... Could it be a default network configuration issue like a limit on tcp packets or a too short timeout ?
