I encountered the same exception on my production server, where I discovered that the Tomcat server was running as three separate processes. This was causing issues while fetching data from the database. To resolve the problem, I stopped all running Tomcat instances and then restarted Tomcat, ensuring that only one instance was running. This successfully resolved the issue in the production environment.