camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sami Nurminen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-11321) Can CamelContext startup faster
Date Tue, 06 Jun 2017 19:48:18 GMT


Sami Nurminen commented on CAMEL-11321:

Could  author meant that Thread.sleep(100) before ss.close() would prevent close throwing
This is just guessing. If there isn't any possibility that ServerSocket could somehow pollute
current thread when closed too early, maybe Thread.sleep could be just removed and any exception
from close ignored.
Also LongAdder could be used for sequence.

> Can CamelContext startup faster
> -------------------------------
>                 Key: CAMEL-11321
>                 URL:
>             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
> 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

View raw message