org.nuxeo.ecm.automation.client.Session holds server resources?

Can anyone explain the behavior of a long-running Automation Session in terms of servers-side resources? We recently received a “Connection pool is fully used” message that mentions nuxeo.vcs.blocking-timeout-millis and nuxeo.vcs.max-pool-size settings. However, we have very few concurrent users at this time and it seems like we should not be hitting pooled connection limits. We do have an integration via the Automation API this is holding open a long-running Session and I'm wondering if that may be related? Should Session's be only kept open for a short period of time or is it OK to keep them open for the long term?

Thanks, Craig

0 votes

0 answers