UNSOLVED Error in logs on hosted fusionauth
I've seen some questions about this in general, but i think normally it's in relation to users that are self hosting.
We're seeing a lot of issues with JWT auth working on one tenant, and the errors i'm seeing in the logs are similar to this (log data truncated): ERROR io.fusionauth.app.primeframework.error.ExceptionExceptionHandler - An unhandled exception was thrown
Error querying database. Cause: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 2000ms.
The error may exist in io/fusionauth/api/domain/TenantMapper.xml
The error may involve io.fusionauth.api.domain.TenantMapper.retrieveById
The error occurred while executing a query
Cause: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 2000ms.
at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30) at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:153) at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:145) at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:140) at org.apache.ibatis.session.defaults.DefaultSqlSession.selectOne(DefaultSqlSession.java:76)
I'm not entirely sure what i could change here myself to be able to resolve this issue; any assistance is welcomed!
@dan this seems to be causing a lot of problems for our app and a corresponding crisis of confidence with fusionauth; is there any way to tell us if it's indicative of an actual issue on the fusionauth hosting side, or if alternatively there's something we can do differently?
dan last edited by
It looks like you are running a few versions back, but I looked through the github issues and didn't find anything that was super close to what you are seeing.
Can you provide any more details? Is this happening with a large number of requests? If so, how many per second?
Are there any event log messages that are helpful?
Does this only manifest in log files or are users seeing 500s (or something else)?
Are there any other operations going on?
Can you see the same issue if you run FusionAuth locally with your config?
Is this reproducible? That's probably the most important question, as that will help us narrow down the issue.
@dan Sorry I didn't get a notification that you'd replied, so my apologies that I didn't see that sooner. I'll try moving to the latest version to see if that helps before reporting back.