No session is available now. Probably the session pool was exhausted.

[Mike Trinh]

Hey guys,

We have different environments for different purposes for our site. The same code is used on all environments, but this problem only occurs on the test environment.

at org.hippoecm.hst.site.request.HstRequestContextImpl.getSession(HstRequestContextImpl.java:172)

at org.hippoecm.hst.site.request.HstRequestContextImpl.getObjectBeanManager(HstRequestContextImpl.java:799)

... 38 more

Caused by: org.hippoecm.hst.core.jcr.pool.NoAvailableSessionException: No session is available now. Probably the session pool was exhausted.

at org.hippoecm.hst.core.jcr.pool.BasicPoolingRepository.login(BasicPoolingRepository.java:348)

at org.hippoecm.hst.core.jcr.pool.BasicPoolingRepository.login(BasicPoolingRepository.java:365)

at org.hippoecm.hst.core.jcr.pool.LazyMultipleRepositoryImpl.login(LazyMultipleRepositoryImpl.java:189)

... 42 more

So this means that there are a lot of sessions active in the basic pooling repository. 

We already upped our configurations as production to maxActive 400(1) and added more memory just to be sure but the problem does still occur..  

The CMS and Console does work, but the /site returns a proxy error.. This happens a lot of times and creates a lot of logs..

There’s probably some setting wrong somewhere, or a configuration on the server wrong. But we checked pretty much everywhere, and have no clue how to solve this issue

Anyone know what else we could do?

Hippo 11.2.2. 

1. https://www.onehippo.org/12/library/concepts/web-application/jcr-session-pooling-repository.html

[Marijan Milicevic]

are you running any stress test on this server? are you using any custom code which uses pooled sessions inside your components?

Also, are there any components connecting to some external services which take long time?

Do you have any custom repository spring XML configurations which might override HST one (similar to ones described in [1] )  

It's really difficult to tell what could be wrong, above mentioned things are just a few (out of many) possible reasons...

Inspecting log entries before above exception occurs could also give you some hints...

cheers

marijan

[1] https://www.onehippo.org/12/library/concepts/web-application/jcr-session-pooling-repository.html

 

Hippo 11.2.2. 

1. https://www.onehippo.org/12/library/concepts/web-application/jcr-session-pooling-repository.html

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-community@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-community+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.