Thanks a bunch Daniel for your help. Also for the patience in answering my question. The solution to this issue to make Tomcat handle the connection pooling instead of the application code OR to restart the application servers along with the DB.
--- On Fri, 20/7/12, Daniel Mikusa <dmik...@vmware.com> wrote: > From: Daniel Mikusa <dmik...@vmware.com> > Subject: Re: java.sql.SQLException: No more data to read from socket > To: "Tomcat Users List" <users@tomcat.apache.org> > Date: Friday, 20 July, 2012, 9:34 PM > ----- Original Message ----- > > Daniel Mikusa wrote: > > ... > > > > > > > > This doesn't look like a Tomcat issue. Your > app is maintaining its > > > own connection pool, it is not using one provided > by Tomcat. I > > > would suggest that you talk with your developers > and see if they > > > can help you. > > > > > Which, after a very long detour, seems to bring us back > to the very > > first answer to this > > thread, doesn't it ? > > Perhaps. While the exception is showing Oracle, which > certainly appears to be the culprit, the user might be able > to mitigate the issue with a configuration option like > "validationQuery". > > Unfortunately the user is not defining a resource in Tomcat, > so it makes it difficult to instruct him how to try adding > such an option. The user would need to check with the > app developer to see about altering the configuration. > > Dan > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
