StackOverFlowError is one of the common confronted JVM error. In this blog post, lets learn inner mechanics of thread stacks, reasons that can trigger StackOverFlowError and potential solutions to address this error. To gain deeper understanding into StackOverFlowError, let's review... Continue Reading →
The latest JAX Magazine issue is out now. The magazine consists of articles that elucidate how digital transformation is reshaping the future of finance. We are happy to share that our founder, Ram Lakshmanan, also contributed an article "The Leprechaun... Continue Reading →
Description Threads in 'runnable' state consume CPU. So when you are analyzing thread dumps for high CPU consumption, threads in 'runnable' state should be thoroughly reviewed.Typically in thread dumps several threads are classified in 'RUNNABLE' state. But in reality several of them wouldn't be actually running,... Continue Reading →
Description Dining Philosophers is a classic computer science problem that happens in concurrent programming. Dining philosophers problem will result in circular deadlock problem. Circular deadlock is a variant of deadlock problem. Once deadlock happens, the only way to recover from... Continue Reading →
Description Wikipedia aptly defines deadlock is a situation in which two or more competing actions are each waiting for the other to finish, and thus neither ever does. If deadlock happens in a JVM, the only way to recover from... Continue Reading →
Description If threads are blocking momentarily, then it’s not a problem. However, if they are blocking for a prolonged period, then it’s of concern. It's indicative of some problem in the application. Typically blocked threads would make application unresponsive. Threads... Continue Reading →
Description You might have experienced the application’s CPU to spike up suddenly & spike wouldn’t go down until JVM is recycled. You restart the JVM, after certain time period CPU consumption would once again start to spike up. Then you will have to... Continue Reading →
Description Thread-A could have acquired the lock-1 and then would never release it. Thread-B could have acquired lock-2 and waiting on this lock-1. Thread-C could be waiting to acquire lock-2. This kind of transitive blocks between threads can make entire application unresponsive. See the real-world... Continue Reading →
Description When there is a performance bottleneck in the application, most of the threads will start to accumulate on that problematic bottleneck area. Those threads will have same stack trace. Thus whenever a significant number of threads exhibit identical/repetitive stack trace then those... Continue Reading →
