[
https://issues.apache.org/jira/browse/CAMEL-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194335#comment-14194335
]
Thomas Diesler commented on CAMEL-7968:
---------------------------------------
Documenting that a shared resource is not thread safe is just as wrong as not
taking greater care about possible concurrent access in the first place. A
client cannot possibly synchronise concurrent access because it may not even be
aware of other clients.
> Container has undefined concurrency behaviour
> ---------------------------------------------
>
> Key: CAMEL-7968
> URL: https://issues.apache.org/jira/browse/CAMEL-7968
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.14.0
> Reporter: Thomas Diesler
> Assignee: Claus Ibsen
> Fix For: 2.15.0
>
>
> The implementation of Container.Instance is not ThreadSafe. It is also not
> defined what happens when multiple Containers race on the singleton.
> Instead of using a Container singleton approach. It might be better to have a
> singleton ContainerRegistry that can handle concurrent/multiple Containers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
