Apache camel CamelContext保持重新启动和关闭

Apache camel CamelContext保持重新启动和关闭,apache-camel,camel-blueprint,Apache Camel,Camel Blueprint,我们正在使用JBoss Fuse 6.3。我们的包通常具有用于数据库连接的属性占位符和其他项目属性。以下是占位符配置的一个示例: <cm:property-placeholder id="property-placeholder-databaseconnection" persistent-id="com.mycompany.database" update-strategy="reload"/> 这种情况经常发生,但并非总是如此。通过搜索web,一些人建议

我们正在使用JBoss Fuse 6.3。我们的包通常具有用于数据库连接的属性占位符和其他项目属性。以下是占位符配置的一个示例:

    <cm:property-placeholder
    id="property-placeholder-databaseconnection"
    persistent-id="com.mycompany.database" update-strategy="reload"/>

这种情况经常发生,但并非总是如此。通过搜索web,一些人建议更改属性占位符中的更新策略=“无”。这一变化确实解决了问题。但是,我们确实希望为某些财产持有人提供updatestrategy=“reload”。此外,我们想知道为什么会发生这种情况。

如果您在多个捆绑包之间共享属性文件,则可能会发生这种情况。是这样吗?请看:@Bedia,你说得对,我们正在进行一个大型集成项目,其中包括多个捆绑包。这些捆绑包共享上述相同的公共属性文件(数据库连接信息和其他公共属性),每个捆绑包都有自己的特定于捆绑包的属性文件我建议您将数据库连接拆分为自己的包。然后,您可以将其作为OSGi服务公开,并将其导入到每个捆绑包中。这将允许您仅引用该捆绑包中的databaseconnection属性文件。@noMad17感谢您的建议。我以后会试试的。
    11:24:44,782 | INFO  | rint Extender: 2 | ManagedManagementStrategy        | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | JMX is enabled
11:24:44,786 | INFO  | rint Extender: 2 | DefaultRuntimeEndpointRegistry   | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Runtime endpoint registry is in extended mode gathering usage statistics of all incoming and outgoing endpoints (cache limit: 1000)
11:24:44,795 | INFO  | rint Extender: 2 | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance.
11:24:44,795 | INFO  | rint Extender: 2 | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
11:24:44,820 | INFO  | rint Extender: 2 | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Route: queuetable-message-router started and consuming from: Endpoint[direct-vm://queuetable-Parentid]
11:24:44,820 | INFO  | rint Extender: 2 | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Total 1 routes, of which 1 are started.
11:24:44,820 | INFO  | rint Extender: 2 | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Apache Camel 2.17.0.redhat-630187 (CamelContext: camelqueuetable) started in 0.076 seconds
11:24:44,825 | INFO  | Thread-3577      | BlueprintCamelContext            | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Apache Camel 2.17.0.redhat-630187 (CamelContext: camelqueuetable) is shutting down
11:24:44,826 | INFO  | Thread-3577      | DefaultShutdownStrategy          | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Starting to graceful shutdown 1 routes (timeout 300 seconds)
11:24:44,827 | INFO  | 9 - ShutdownTask | DefaultShutdownStrategy          | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Route: queuetable-message-router shutdown complete, was consuming from: Endpoint[direct-vm://queuetable-Parentid]
11:24:44,827 | INFO  | Thread-3577      | DefaultShutdownStrategy          | 232 - org.apache.camel.camel-core - 2.17.0.redhat-630187 | Graceful shutdown of 1 routes completed in 0 seconds