Then we need: - full boot logs - a thread dump when it is slow - maybe debug logs to check connections are closed
Le 8 août 2016 21:21, "semanticfire" <[email protected]> a écrit : > Error codes from oracle: > > > > I don't see anything out of the ordinary in the JMX logging > > > semanticfire wrote > > Hi, > > > > I don't see any errors, other then it seems the startup seems somewhat > > slow. > > I'll look at the JMX connection logs again. > > > > Configuration: > > > > > Bart > > Romain Manni-Bucau wrote > >> Hi > >> > >> Tomcat jdbc got some param renaming. Check warnings at startup, it > should > >> be logged. > >> > >> Also maybe monitor through jmx the number of active connections per > >> invocation of the method to ensure it is released. > >> > >> Le 8 août 2016 20:26, "semanticfire" < > > >> bart@ > > >> > a écrit : > >> > >>> Hi, > >>> > >>> I run a webapp which uses polling through Quartz to query a ORACLE > >>> Database. > >>> > >>> When I use a plain Tomee+ 7.0.1 server I run into cursor errors on the > >>> JDBC > >>> connection. > >>> using the same war on a Tomee+ 1.7.4 works without issues. > >>> > >>> Any hints would be welcome > >>> > >>> Bart van Leeuwen > >>> > >>> > >>> > >>> -- > >>> View this message in context: http://tomee-openejb.979440. > >>> n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654.html > >>> Sent from the TomEE Users mailing list archive at Nabble.com. > >>> > > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Changes-in-JDBC-1-7-4-7-0-1-tp4679654p4679659.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
