[CAMEL-15061] Performance issues with classMap.computeIfAbsent() in DefaultFactoryFinder

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.25.2, 3.4.0
• Component/s: camel-core, karaf
• Estimated Complexity: Unknown
• Assignee: Grzegorz Grzybek
• Reporter: Grzegorz Grzybek
• Created: 14/May/20 09:36
• Updated: 14/May/20 15:33
• Resolved: 14/May/20 14:35

Description

When Camel routes start, there are unnecessary calls from class DefaultFactoryFinder in method

   protected Class<?> addToClassMap(String key, ClassSupplier mappingFunction) throws ClassNotFoundException, IOException  {
        try {
            return classMap.computeIfAbsent(key, (String classKey) -> { ...

In a Karaf environment with the Java security manager enabled, this causes a massive delay in starting Camel routes, since there are thousands of calls into org.apache.felix.framework.BundleImpl.getEntry(), which is then authorised by the Java Security Manager. Its seems a bulk of these calls could be avoided if the call to classMap.computeIfAbsent() dealt with null values as well.

Issue Links

• links to: GitHub Pull Request #8
• links to: GitHub Pull Request #3825
• links to: GitHub Pull Request #3826