[
https://issues.apache.org/jira/browse/CAMEL-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13125:
-------------------------------------
Description: We have the same situation of CAMEL-13123 on camel-mongodb,
even though it has been deprecated (was: [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.)
> Camel-MongoDB: Endpoint shutdown closes mongo connection, killing the
> connection for everyone
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-13125
> URL: https://issues.apache.org/jira/browse/CAMEL-13125
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
> Affects Versions: 2.23.1
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 2.21.5, 2.22.3, 2.23.2, 2.24.0
>
>
> We have the same situation of CAMEL-13123 on camel-mongodb, even though it
> has been deprecated
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
