We would like to extend our thanks to Entwinkler.de JavaMagazin for translating and publishing our article ‘Simulating and troubleshooting deadlocks in Kotlin’ in the German language. It is an honor to have our work published in a print magazine, that too in German language.
Continue reading “Simulation und Fehlerbehebung von Deadlocks in Kotlin – Bahnbrechende Deadlocks”In this series of simulating and troubleshooting performance problems in Kotlin, let’s discuss how to simulate the ‘java.lang.OutOfMemoryError: Java Heap space’ problem. ‘java.lang.OutOfMemoryError: Java Heap space’ will be thrown by the application, when it generates more objects than the maximum configured heap size.
Continue reading “Simulating & troubleshooting OOMError in Kotlin”In this series of simulating and troubleshooting performance problems in Scala, let’s discuss how to simulate StackOverflowError. StackOverflowError is a runtime error, which is thrown, when a thread’s stack size exceeds its allocated memory limit.
Continue reading “Simulating & troubleshooting StackOverflowError in Scala”In this post let’s discuss an interesting memory problem we confronted in the production environment and how we went about solving it. This application would take traffic for a few hours after that it would become unresponsive. It wasn’t clear what was causing the unresponsiveness in the application.
Continue reading “Memory leak due to improper exception handling”Learn how to troubleshoot OutOfMemoryError using the Eclipse MAT tool. You will learn best practices, cool tips & tricks to debug memory problems effectively. Watch this video to know more!
Continue reading “Troubleshooting OutOfMemoryError – Heap dump, Eclipse MAT”Buggy App is a simple java application that simulates different performance problems like Memory Leak, OutOfMemoryError, CPU spike, thread leak, StackOverflowError, deadlock, unresponsiveness, …
Continue reading “Buggy App – Simulate performance problems”Recently we experienced an interesting production problem. This application was running on multiple AWS EC2 instances behind Elastic Load Balancer. The application was running on GNU/Linux OS, Java 8, Tomcat 8 application server. All of sudden one of the application instances became unresponsive. All other application instances were handling the traffic properly. Whenever the HTTP request was sent to this application instance from the browser, we were getting following response to be printed on the browser.
Continue reading “TCP: out of memory — consider tuning tcp_mem”