Scenario to reproduce:
- start DB in VM
- start Nuxeo
- try to access and perform operations on UI -> OK
- pause DB
- try to access and perform operations on UI -> KO
- resume DB
- try to access and perform operations on UI -> OK
- stop DB in the VM but keep the VM up
- try to access and perform operations on UI -> KO
- start DB
- try to access and perform operations on UI -> KO
- this gives the following stack trace:
2016-10-11 15:20:00,209 ERROR [Quartz_Worker-1] [org.nuxeo.ecm.core.event.impl.EventServiceImpl] Exception during triggerEsclationRules sync listener execution, continuing to run other listeners org.nuxeo.ecm.core.api.NuxeoException: Connection pool is fully used, consider increasing nuxeo.vcs.blocking-timeout-millis (currently 100) or nuxeo.vcs.max-pool-size (currently 20) at org.nuxeo.ecm.core.storage.sql.ra.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:108) at org.nuxeo.ecm.core.storage.sql.ra.ConnectionFactoryImpl.getSession(ConnectionFactoryImpl.java:159) at org.nuxeo.ecm.core.repository.RepositoryService.getSession(RepositoryService.java:230) at org.nuxeo.ecm.core.api.local.LocalSession.createSession(LocalSession.java:117) at org.nuxeo.ecm.core.api.local.LocalSession.connect(LocalSession.java:83) at org.nuxeo.ecm.core.api.CoreInstance.acquireCoreSession(CoreInstance.java:184)
- is related to
-
NXP-20623 infinite loop in pool validation interceptor
- Resolved