jbonofre commented on issue #576: URL: https://github.com/apache/camel-karaf/issues/576#issuecomment-2593919408
Thanks for the report. The resolver probably find multiple resolution chains and that's why it consumes CPU. It can happen depending of the feature install order (race condition). With the details you provided, I will try to reproduce. FYI, in Karaf 4.5.x, I'm working on a new resolver that should avoid this kind of problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
