You need to repair this. There are a few ways to deal with this but in general how do you know when the customer system (for lack of a better term) is done loading your queue? The entire purpose of the queue is to allow for eventual data transmittals. Can the Customer System send ...
Then, after development & qa, we were getting ready for the production release and more extensive testing with production level data started. We got blocks, deadlocks, timeouts... It was a horrifying nightmare. We had to rewrite the entire data access layer into regular old SELECT statements ...
In the last couple of years, I've eliminated nearly 3 days per day of CPU time and a couple of hundred trillion bytes of IO on our "money maker" system and it's really helped with timeouts and deadlocks on the user end a whole lot. That's the problem with such things. No one th...
As our business volume increases, we seem to be getting more issues like deadlocks and (ADO.Net) timeouts. We can't go back and overhaul 15 years of application coding all at once; however for new or updated app there might be places were dirty reads would be unacceptable but snapshot w...
so any one attacking IP only hits one username once. Note that timing out an IP after three consecutive failed attempts can really irk the clients/customers of a public web site if one company/ISP/etc has 20,000 people behind a single external IP address. Timeouts like that are almost alw...
I'd go to 2-3 timeouts for managers or catchers to walk out and talk. Other than that, if you want a pitching change, signal it. No mound visits. Only enough warm up pitches for a new pitcher to fit in 30s commercial spot. Set a time between innings, maybe 2.5 minutes (4 ...
The database developer can, of course, throw all errors back to the application developer to deal with, but this is neither kind nor necessary. How errors are dealt with is very dependent on the application, but the process itself isn't entirely obvious.