camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoran Regvart (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11261) Revise Camel context destruction in Spring (Boot) applications
Date Mon, 29 May 2017 12:22:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-11261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028279#comment-16028279
] 

Zoran Regvart commented on CAMEL-11261:
---------------------------------------

The issue in wildfly-camel was that the startup of {{SpringCamelContext}} was inhibited by
the {{noStart}} flag. The reasoning is that Wildfly as an application server should control
when a subsystem is started or stopped. I think we should have a discussion if we can eliminate
the {{noStart}} flag as it is global for all {{SpringCamelContext}}'s (in the same classloader)
and instead of that use {{isAutoStartup}} flag or create a new flag that replaces {{noStart}}
flag but at a per {{CamelContext}} level.

> Revise Camel context destruction in Spring (Boot) applications
> --------------------------------------------------------------
>
>                 Key: CAMEL-11261
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11261
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring, camel-spring-boot
>            Reporter: Zoran Regvart
>            Assignee: Zoran Regvart
>            Priority: Critical
>             Fix For: 2.20.0
>
>
> There have been issues in the past where the user needs to control the destruction order
of CamelContext with regards to other dependencies. Notably resources such as connection pools.
AMQ-3988 notes one of those for JMS connection pools.
> Prompted by the [discussion|http://camel.465427.n5.nabble.com/OnApplicationEvent-not-called-with-CamelAutoConfiguration-tp5798802.html]
on the user forum we should investigate if there is a way we can get CamelContext priority
on shutdown.
> One idea is to use lifecycle beans as in [PR#1685|https://github.com/apache/camel/pull/1685].
> We should evaluate if this change introduces other issues.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message