Ouch. Thanks, Dan. We are rolling out 3.3.0 at work. Should I hold off until 3.3.1? Do we think this has a high likelihood to cause performance issues? On Fri, Feb 15, 2019 at 9:17 AM Daniel Kulp <[email protected]> wrote:
> > > On Feb 14, 2019, at 3:42 PM, James Carman <[email protected]> > wrote: > > Is this just impacting folks that use JAXB or is this more pervasive? > > > Actually, the reverse is likely more of an issue, but it's pervasive no > matter what. If you do have jaxb and all the other related things > (activation, etc..) classes, the Class.forName calls should be quicker as > the first time it’s called the class would get loaded and it should return > relatively quick. > > The big issue is if the class.forName fails, we will keep calling it every > request. On some class loaders (OSGi for example), class.forName is very > expensive for classes it cannot find as it searches major hierarchies of > class loaders trying to find it. And it does this over and over and over > for each request. > > Dan > > > > > On Thu, Feb 14, 2019 at 8:02 AM Cocorossello <[email protected]> > wrote: > > > Hi, > > Thanks for the patch. I've tried in dev and I can see no major locks. > Although I haven't tested in production, I'll try to push a build with cxf > 3.3.0 and this class patched, but I can't promess anything. > > Best regards, > Vicente. > > > > -- > Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://talend.com <http://coders.talend.com> > >
