Is VCS aware of multi-threaded pool connections when closing pooled resources?

New question as a continuation of this question.

Error is:

11936 2012-05-16 09:59:58,397 ERROR [org.hibernate.util.JDBCExceptionReporter] Cannot get a connection, pool error Timeout waiting for idle object

I did a bit of research and found (this) tutorial on connection pool leaks within TomCat.

If you look at the section entitled: Common Problems in the above link you will see a suggested way to return (close) pooled db connections.

My Question is does VCS use a similar techniques to prevent pool exhaustion/leaks from multi-threaded processes when multiple documents are created within a short period (seconds) of time in the same folderish document? Also, I do not see, in the TOMCAT db resource configuration file, that nuxeo (VCS) uses removeAbandoned=“true” to clean up abandoned connections. I'm I missing something?

0 votes

0 answers



I noticed the following error in the log:2012-05-17 09:36:05,894 INFO [org.jbpm.persistence.db.StaleObjectLogConfigurer] stale object exceptions will be hidden from logging

How can I view these "hidden" objects? Are they relevant to this problem?