Hi Amit, AFAIK it is not known but from the JIRA ticket [1] it seems due to the WF implementation which uses EMF#getProperties more than we expected. Master fixes that (openjpa 3.1.3-SNAPSHOT) if so but since it is the EAP, JBoss should be able to solve that for you by not doing any assumption on this method performance (they assumed it was a o(1) as in hibernate but we are a bit slower in v <= 3.1.2) and caching the result of the first test. Will work for all JPA impl if updated this way. That said the coming 3.1.3 should fix that too.
[1] https://issues.apache.org/jira/browse/OPENJPA-2834 Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 1 oct. 2020 à 15:43, AMiT YADAV <camitya...@gmail.com> a écrit : > Team, > Hope you all are safe and healthy. > > We are facing a huge performance issue with *OpenJPA-3.1.1 *when we deploy > our application in *EAP 7.3* Server but a similar issue is not replicated > with Wildfly-10.1.0 server with the same version. > Is this a known issue? How can we resolve this? Which openjpa jar we should > use with EAP 7.3? > > Please do the needful. > > > *Kind regards,*Amit Yadav >
