Interesting. still having a hard time to see why it is that slow - do you run with a security manager?. What can be way slower is the fact tomee 7.0.2 activate CDI for JPA is the provider supports it so this can slow down it since a "new X()" will become a CDI lookup. Can you try setting tomee.jpa.cdi=false in your persistence unit or as a system property to see if it helps?
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-01-27 13:40 GMT+01:00 cocorossello <[email protected]>: > The problem has to be in JTAEntityManager.isJPA21, now is much slower. > > org.apache.openejb.persistence.JtaEntityManager.<init> (String, > org.apache.openejb.persistence.JtaEntityManagerRegistry, > javax.persistence.EntityManagerFactory, java.util.Map, boolean, String) > 91.7 > ms (0.3%) 10,206 ms (1%) > > org.apache.openejb.persistence.JtaEntityManager.isJPA21 > (javax.persistence.EntityManagerFactory) 20.0 ms (0.1%) 10,063 ms > (1%) > > > org.apache.openejb.persistence.JtaEntityManager.hasMethod (Class, String, > Class[]) 575 ms (2%) 984 ms (0.1%) > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Tomee-7-0-2-performance-tp4680954p4680957.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
