-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The prod 'verta-backend-0' becomes failed after a few hours #1539
Comments
Our configuration follows this repository. Now, most of the time it's working well, but this error will occur in a few hours or in a day. |
@tatianguiqu : it is trying to establish connection with postgres but can not establish one.
|
@ravishetye When I wanted to observe the log and database when bugs happened, it didn't make any mistakes for more than four days. I'm still waiting, but there was always an exception in one day before. It's confusing. |
The prod 'verta-backend-0' kept running for 17 days without becoming failed. It is so confused. But there were 500 server errors in deploying the service today. After I restarted the prod, the problem was solved. The error log of prod 'verta-backend-0' is following: |
The log says 'sorry, too many clients already'. Is it caused by too many open hibernate sessions? |
I face the same case where my deploy version is 1.0.8.1 |
The prod works well at first, but it always breaks down after a few hours. Then it t starts printing logs indefinitely:
{"thread":"pool-3-thread-1","level":"WARN","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil checkDBConnection() got error ","thrown":{"commonElementCount":0 │ {"thread":"pool-4-thread-1","level":"DEBUG","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil getSessionFactory() retrying for DB connection after 2560 milli │ {"thread":"pool-4-thread-1","level":"WARN","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil checkDBConnection() got error ","thrown":{"commonElementCount":0 │ {"thread":"pool-3-thread-1","level":"DEBUG","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil getSessionFactory() retrying for DB connection after 2560 milli │ {"thread":"pool-4-thread-1","level":"DEBUG","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil getSessionFactory() retrying for DB connection after 2560 milli │ {"thread":"pool-3-thread-1","level":"WARN","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil checkDBConnection() got error ","thrown":{"commonElementCount":0 │ {"thread":"pool-4-thread-1","level":"WARN","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil checkDBConnection() got error ","thrown":{"commonElementCount":0 │ {"thread":"pool-4-thread-1","level":"DEBUG","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil getSessionFactory() retrying for DB connection after 2560 milli │ {"thread":"pool-3-thread-1","level":"DEBUG","loggerName":"ai.verta.modeldb.utils.ModelDBHibernateUtil","message":"ModelDBHibernateUtil getSessionFactory() retrying for DB connection after 2560 milli
This error seems to be caused by this call path: ai.verta.modeldb.utils.ModelDBHibernateUtil.checkDBConnectionInLoop()-> checkDBConnection()-> getDBConnection()->Class.forName(rDBDriver)
Because enableTrace is not enabled, RdbDriver is configured as "org.postgresql.Driver".
It's confusing to make mistakes there after a few hours.
The text was updated successfully, but these errors were encountered: