Eclipse Community Forums: EclipseLink » Wildfly 10 - The cost of creating the first eclipselink EntityManager during deployment is extremell

Home » Eclipse Projects » EclipseLink » Wildfly 10 - The cost of creating the first eclipselink EntityManager during deployment is extremell

Show: Today's Messages :: Show Polls :: Message Navigator

Wildfly 10 - The cost of creating the first eclipselink EntityManager during deployment is extremell [message #1773674]

Mon, 02 October 2017 16:40

Nuno Godinho de Matos

Messages: 34
Registered: September 2012

Member

Plase see thread:
https://issues.jboss.org/browse/WFLY-9408

The class:
org.eclipse.persistence.platform.server.JMXServerPlatformBase

Needs to be fixed.
The source code behind
public MBeanServer getMBeanServer() {

is a total deployment killer.

The log statements that do something like:
mBeanServer.getMBeanCount()

Are costing seconds upond seconds to the deployment of JEE applications.
This happens at the very least on wildfly, I have not confirmed if the API would be fast on weblogic.

This issue needs to be fixed . This is really critical, because no Log statement can justify such an extremly high impact to deployment time.

Many thanks for taking a look.

Report message to a moderator

Previous Topic:	How to use JPA and Hibernate together with Tomcat 8?
Next Topic:	Extra criteria on ManyToMany relation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Sep 26 05:57:03 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter