> On Feb 11, 2019, at 6:13 AM, Cocorossello <[email protected]> wrote: > I've been checking my app with JFR. I can see a new important lock since CXF > 3.3.0 coming from ProviderFactory.tryCreateInstance that changed, the > commit is > https://github.com/apache/cxf/commit/791461c6f957ebd466b432c354c15e91500cf463#diff-556a2e3b0d567e80dbcc125b0c19da8a > > Is it a problem? Here is a screenshot of the JFR report that I extracted by > recording 120 seconds in production (don't mind the IndirectList lock, I > know why it happens, it's "ok"). https://imgur.com/J4xuGjb
Yea… I consider it a problem. You may be able to limit it by adding the various classes that are needed by the providers so that the class loader itself can actually cache the class objects (instead of repeated class not found issues), but it’s still calling into synchronized methods which would cause contention. I’ve just pushed a change to master (3.3.1-SNAPSHOT) that I hope will resolve this by caching the Class objects (or the fact that the class objects are null if they cannot be loaded). That should eliminate this problem. It would be great if you could give it a try. -- Daniel Kulp [email protected] <mailto:[email protected]> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://talend.com <http://coders.talend.com/>
