Hello Faisal, It looks like your problem is more related with your hikari connection pool than with tomcat itself. I would recommend you to double check your hikari configuration properties. Pay specially attention on how you are configuring your connection pool (minimum and maximum size, timeout, etc...) It looks like there is "something" in your application that prevents to get connections from your pool.
Hope it helps, Luis El lun., 18 feb. 2019 a las 6:33, <fai...@bestercapitalmedia.com> escribió: > Dear all, > > > > I am working on a project and I am facing following issue on almost every > second day. I need to restart tomcat to get it running again. > > Can someone guide me on it. Ask if you need some other insight to look into > it. > > > > 2019-02-18 04:49:35.572 WARN 20698 --- [io-4200-exec-15] > o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 0, SQLState: null > > 2019-02-18 04:49:35.572 ERROR 20698 --- [io-4200-exec-15] > o.h.engine.jdbc.spi.SqlExceptionHelper : HikariPool-1 - Connection is not > available, request timed out after 30000ms. > > 2019-02-18 04:49:35.573 WARN 20698 --- [io-4200-exec-15] > o.s.s.o.provider.endpoint.TokenEndpoint : Handling error: > InternalAuthenticationServiceException, Unable to acquire JDBC Connection; > nested exception is org.hibernate.exception.JDBCConnectionException: Unable > to acquire JDBC Connection > > > > Server is Ubuntu (aws) > > Database is mySql > > java version "1.8.0_181" > > Java(TM) SE Runtime Environment (build 1.8.0_181-b13) > > Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) > > > > Best Regards | Bien Cordialement | تحياتي > > Faisal Zaidi > Application Architect > > > > -- "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better." - Samuel Beckett
