I was surprised to witness the Java Executor behavior – which caused “java.lang.OutOfMemoryError: unable to create new native thread” in our application. I would like to share my surprise (i.e. problem) and resolution to it.
Configuring a database connection pool is vital for application performance, balancing resource usage and response time. Recommended practices include setting the max pool limit to peak traffic, defining a finite connection checkout wait period, utilizing the LIFO algorithm for checking out connections, and establishing an ideal idle timeout period, typically around five minutes.
The application using DataStax's Java driver to connect with Apache Cassandra faced a 'java.lang.OutOfMemoryError' due to an excessive number of runnable threads, linked to the netty library. This issue arose when Cassandra ran out of space, highlighting the need for client applications to handle such scenarios more resiliently without resulting in OutOfMemoryError.