Imagine you're each operations guy and you've merited received a phone call or alert notifying you that the reference to practice you're responsible for is running tardy. You bring up your console in your JVM monitoring tool, interference all related processes, and notice any java.exe process is hogging toty the CPU on one box. The medial sum sys admin at this point would fair kill and restart the Java process, cross their fingers, and hope everything returns to erect, and this actually works most of the time. The putting into practice returns to normal, and you appropriate yourself on the back for a job well done.
This story may strike one as being contrived, but it happens all the time. The substantiality is that no one in operations has the time or perceptibility to figure out the real impression behind issues like this. Little embarrassment is applied to development to provide the root cause to prevent produce slowdowns in the future. Restarting the JVM is plenty, because it appears to solve the point in dispute. In fact, it's only a ephemeral fix that hides the real problems in the intense study logic and configuration.
No comments:
Post a Comment