[
https://issues.apache.org/jira/browse/CAMEL-11321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024516#comment-16024516
]
Claus Ibsen commented on CAMEL-11321:
-------------------------------------
This is done only once, but we wait 100 millis on startup of the AMQ uuid
generator
https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/impl/ActiveMQUuidGenerator.java#L82
This code is using the same uuid logic from AMQ to be unique and similar. That
sleep is maybe needed to wait to close the ServerSocket.
Though its an interesting approach to use ServerSocket to generate uid id. But
we could consider a faster implementation without a sleep
> Can CamelContext startup faster
> -------------------------------
>
> Key: CAMEL-11321
> URL: https://issues.apache.org/jira/browse/CAMEL-11321
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring-boot
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> [~lb] have some thoughts on if we can make CamelContext startup faster,
> especially when using Spring Boot. Spring Boot itself is not so fast, but
> should be faster in 2.x.
> For example we could consider camel-core to not do any classpath scanning for
> components that are provided OOTB in camel-core, eg if using "log" endpoint,
> then only check the spring registry if any custom bean of that, and if not,
> then we know "log" is from camel-core and then we know its class name already
> and dont need to scan the classpath.
> We could take that one step further for the entire Camel release and have a
> plugin that generate/keep java source file up to date from camel-core, which
> has complete mapping of all component-name=component-class.
> We can also do some profiling and see if there is some hot-spots. There is
> also the revised work that Zoran does in starting Camel on spring /
> spring-boot.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
