Possible bug: Nuxeo doesn't clear the connection pool after 10 minutes
We're testing our Nuxeo 6.0 and we've detected that it doesn't clear the connection pool when we use Funkload to benchmark it. After a Funkload test against Nuxeo 6.0 the pool reach his limit and Nuxeo can not accept more connections, it throws an exception. After 20 minutes waiting the connection pool is full yet.
Nuxeo says that active connections is 20. I've configured in nuxeo.conf session.timeout=1, but it doesn't solve the problem.
Do you know why?
Thank you, Gabriel
If I log to Nuxeo vm, browse to Repository statistics tab in admin center and press repeatedly 'F5', I get the connection pool to its maximum. The counter open connections on the repository also increases with each refresh.
In previous versions connections didn't increase.
I think Session Management changed in Nuxeo 6.0. Is this a bug or the expected behaviour?
We also noticed that connecting through JMX IdleTimeoutMinutes is 0 for the pool. It apparently ignores the parameter nuxeo.vcs.idle-timeout-minutes.
jdbc/nuxeo still has idletimeout equals to zero.
We still don't understand conversationId behaviour and some problems with funkload.