I created a console application that it should run every hour in order to push updates to a different server using FluorineFx for C# client (NetConnection). It works great, but only when I have Charles open and so I can see what is being sent. On the other hand, if Charles is closed, it does not send the data.
Thx.
I am a bit late to the party, but I recently encountered the same problem and found a solution. The issue is that Fluorine does not call the Close() method on the HttpWebResponse objects and as a result .NET keeps the object alive indefinitely, which causes subsequent requests to eventually block on the default connections-per-host limit.
I found two such cases in RemotingClient.cs, calling HttpWebResponse.Close() after you are done with the response fixed the problem for me.