Regular Cayenne operations should not leak connections. Any connections Cayenne gets are closed (== returned to the pool) regardless of whether an operation succeeds or fails. The only exception is iterated queries that require the caller to close Cayenne ResultIterator, so bugs in the user code can lead to connection leaks.
FWIW, I've also been using Tomcat connection pool for many years, both in Bootique and more traditional Jetty apps. Never seen a problem that you describe. What are the connection pool settings? Andrus > On May 8, 2017, at 10:57 PM, Markus Reich <markus.re...@markusreich.at> wrote: > > Hi, > > I have a problem with our JNDI DataSource (Catalina Connection Pool). > After a while I got a lot of active conns in the Pool (I can see them in > via JMX), when I take a look in Oracles v$session, all sessions/conns are > in IDLE state? > The Problem is, that the pool thinks all sessions are active so he creates > new ones, so we have a lot of sessions created in Oracle, nearly about 1 > session / per second!!! > > Has anybody experiences with Oracle and Cayenne and Tomcat Connection > Pooling? > Is there any way I get more infos, logs, traces? > > thx > Markus
