You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2019/01/24 15:08:00 UTC
[jira] [Updated] (CAMEL-13123) Endpoint shutdown closes mongo
connection, killing the connection for everyone
[ https://issues.apache.org/jira/browse/CAMEL-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino updated CAMEL-13123:
-------------------------------------
Priority: Major (was: Blocker)
> Endpoint shutdown closes mongo connection, killing the connection for everyone
> ------------------------------------------------------------------------------
>
> Key: CAMEL-13123
> URL: https://issues.apache.org/jira/browse/CAMEL-13123
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb3
> Affects Versions: 2.23.1
> Reporter: Peter Nagy
> Priority: Major
>
> [This piece of code in MongoEndpoint|https://github.com/apache/camel/blob/21bb980d29cdb7f09d875f8278fcf1d21f785ea0/components/camel-mongodb3/src/main/java/org/apache/camel/component/mongodb3/MongoDbEndpoint.java#L302] closes the underlying MongoClient object when an Endpoint gets stopped. This is not correct behavior. There most probably are other endpoints using the client and this closes the connection for all of them. So if route1 stops and route2 is using the same MongoClient (from the registry) then route2 just got nuked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)