I've app, which use the database in multiple concurrent sessions (over 1000). In Postgres the max connections available is set to 100 by default and i haven't change this.
Hibernate has max connection pool size is 20, but the app seems to be ignored this and throws "Too many connections" error.
So the problem is how to handle over 1000 sessions when the only available is 100? Is there queue or smth like this is possible?
Hibernate has max connection pool size is 20, but the app seems to be ignored this and throws "Too many connections" error.
Double check your use of Hibernate Session Factory:
Often the problem is the bad usage of Hibernate Session.
[1] https://developer.jboss.org/wiki/UsingHibernatewithTomcat [2] http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html/ch01.html#tutorial-firstapp-workingpersistence
So the problem is how to handle over 1000 sessions when the only available is 100? Is there queue or smth like this is possible?
100 are the concurrent connection that you can open, over these you can do more than 100 operations: Hibernate just manage the queue for you.
.openSession() to .getCurrentSession();.. etc, as it described there. But there's no effect. In the app every session creates from different threads at the same time (1000 threads=1000 sessions) and .getCurrentSession() creates new one session anyway like .openSession() does. In this case, ofc 1000sessions will hit over db connection restriction and the error will be thrown. Thats why i want to queue this. But Hibernate seems dont want to manage this for me :(Hibernate doesn't support nested transactions error