Identify and Aid Customers with Production Live-Locks
There's the concept of a "dead" lock and a "live" lock. A live-lock is essentially a race condition within a production environment. It causes stair stepping of CPU usually until the server crashes.
This often happens when a developer accidentally uses a non-thread safe object in a multi-threaded manner.
The object (for example a HashSet) being used needs to be identified and a thread safe type needs to be replaced so that the live-lock goes away and the CPU goes back to normal.
1
vote
AdminJeff Fischer
(Lead Problem Developer, Optimizely)
shared this idea