[
https://issues.apache.org/jira/browse/CAMEL-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985499#comment-14985499
]
Nicholas Stuart commented on CAMEL-9161:
----------------------------------------
Ok, so it looks like I found the root cause, as it is also happening in 2.15.3.
The culprit is in the changes in RoutesCollectors:
if (applicationContext.getParent() == null) {
...
}
https://github.com/apache/camel/commit/21107ffe44ff88828a4f8bcc777ec7797e885c5f#diff-dc33e1af06d90575702e3c156abde0c4
In my app, the application parent is indeed, not null. I'm not sure what the
reasoning behind this parent check is (besides aforementioned double refresh).
Will investigate further to see if I can come up with a solution for us, but
just thought I would share my findings so far.
My parrent context, btw, is a AnnotationConfigApplicationContext which doesn't
seem to out of the ordinary.
> Camel spring-boot not finding routes.
> -------------------------------------
>
> Key: CAMEL-9161
> URL: https://issues.apache.org/jira/browse/CAMEL-9161
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
> Affects Versions: 2.15.3
> Reporter: Nicholas Stuart
> Assignee: Henryk Konsek
>
> On startup Camel is not registering any routes annotated with @Component.
> Route is found and registered in Spring just fine. Switch to version 2.15.2
> and it works fine.
> No errors are thrown, and everything says it's started, but no routes are
> active or reported as being found during startup.
> Application is being run through `mvn spring-boot:run` if that makes a
> difference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
