can you add the stack as well (new Exception().printStackTrace())? would help to see where it leaks from
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-02-10 15:43 GMT+01:00 tschuler <[email protected]>: > Hi Romain! > > We actually cannot reproduce the issue within a small example. > > But what we did was "enhancing" ManagedConnection.java with log messages > in case of connection is created or closed. > Attached text file (startAgent2.log) includes the additional log messages > showing that three connections are opened (Thread "http-nio-28080-exec-5" - > ConnectionID 30, 29 & 28) but not closed any more. > > Maybe that helps identifying the root cause. > If you have a "log message enhancement" suggestion - we'll add it. > > Best regards, > Thomas > > > startAgent2.txt (14K) <http://tomee-openejb.979440. > n4.nabble.com/attachment/4681052/0/startAgent2.txt> > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/TomEE-7-0-2-increasing-quartz-tx-database- > connections-tp4681007p4681052.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
