I have an ASP.NET web API that has been in production for several years and that has seen literally dozens of updates. Suddenly, after minor changes to the API code, it crashes after exactly 50 requests , regardless of which browser or client is being used. Restarting the web server immediately restores the availability of the API (reusing the application pool), but the mysterious countdown starts again ...
This strange effect persists on multiple machines (Windows Server 2008, Windows Server 2013 and Windows 7) and on different web servers (IIS 7.5, IIS 8.5, UltiDev Web Server). IDE - Visual Studio 2015 community; The .NET version is 4.5.2.
I have not added external API dependencies. I suspect Firebird (the only external dependency) imposes this limit of "50", but all my experiments and searches have been unsuccessful.
Only one useful log message that I could extract said that the database connection was due to a timeout error . (I use Firebird 2.5 SuperServer x64 and Firebird.NET Provider with the FirebirdSql.Data.FirebirdClient.dll file version 3.0.2, which so far has helped me.) However, I can connect to the database and view it through FlameRobin. In any case, everything works fine as soon as I get back to the previous version of the API.
After a crash, the previously cleared firebird.log contains 50 identical messages, similar to this:
AB-01234-CD (Server) Fri Nov 25 14:22:57 2016
INET/inet_error: read errno = 10054
, . / , Firebird. -.
...