Re: HikariCP problems with Tomee
Le 19 sept. 2016 16:14, "tonywestonuk" a écrit : > > Further investigation leads me to believe that it only happens when running > TomEE from within Eclipse. Running tomee as a standalone and dropping / > taking out the war works fine. > > > I know Eclipse does some weird crap to the Environment So, not really > surprised I guess. > > +1, their lifecycle is surely broken for us :( > > -- > View this message in context: http://tomee-openejb.979440.n4.nabble.com/HikariCP-problems-with-Tomee-tp4680148p4680150.html > Sent from the TomEE Users mailing list archive at Nabble.com.
Re: HikariCP problems with Tomee
Further investigation leads me to believe that it only happens when running TomEE from within Eclipse. Running tomee as a standalone and dropping / taking out the war works fine. I know Eclipse does some weird crap to the Environment So, not really surprised I guess. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/HikariCP-problems-with-Tomee-tp4680148p4680150.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: HikariCP problems with Tomee
This is typical of a thread leak - likely in hikari pool there or bad shutdown in predestroy. Le 19 sept. 2016 15:35, "tonywestonuk" a écrit : > Hi. I am using Hikari Connection pool, creating a pool in a @postconstruct > method, and closing it in a @predestroy method. > > I am getting an exception when I remove the web app instance: > > > java.lang.NoClassDefFoundError: java/util/concurrent/ScheduledFuture > at com.zaxxer.hikari.pool.PoolEntry.close(PoolEntry.java:173) > ... > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [java.util.concurrent.ScheduledFuture]. The following stack trace is > thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > > > Im not sure if this is an issue with HikariCP, or TomEE. However, it seams > to me that the problem is that Hikari is attempting to load > ScheduledFuture, > and TomEE is saying NO, the webapp has been shutdown. > > Should TomEE be denying loading of classes in the @PreDestroy method, as > the > webapp hasn't actually been shutdown (yet)? > > Thanks. > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/HikariCP-problems-with-Tomee-tp4680148.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
HikariCP problems with Tomee
Hi. I am using Hikari Connection pool, creating a pool in a @postconstruct method, and closing it in a @predestroy method. I am getting an exception when I remove the web app instance: java.lang.NoClassDefFoundError: java/util/concurrent/ScheduledFuture at com.zaxxer.hikari.pool.PoolEntry.close(PoolEntry.java:173) ... Caused by: java.lang.ClassNotFoundException: Illegal access: this web application instance has been stopped already. Could not load [java.util.concurrent.ScheduledFuture]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. Im not sure if this is an issue with HikariCP, or TomEE. However, it seams to me that the problem is that Hikari is attempting to load ScheduledFuture, and TomEE is saying NO, the webapp has been shutdown. Should TomEE be denying loading of classes in the @PreDestroy method, as the webapp hasn't actually been shutdown (yet)? Thanks. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/HikariCP-problems-with-Tomee-tp4680148.html Sent from the TomEE Users mailing list archive at Nabble.com.
