]
Mircea Markus commented on ISPN-2876:
-------------------------------------
[~dan.berindei] so adding synchronised around get component should solve the problem
then?
AbstractComponentRegistry.getComponent can return an incomplete
component
-------------------------------------------------------------------------
Key: ISPN-2876
URL:
https://issues.jboss.org/browse/ISPN-2876
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.2.Final
Reporter: Dan Berindei
Assignee: Mircea Markus
Fix For: 6.0.0.Final
AbstractComponentRegistry.getComponent doesn't have any locking, so it's possible
for a thread to retrieve a component while another thread is injecting that
component's dependencies.
Normally this isn't a problem, because the global registry is locked during cache
manager startup, and the cache registry is locked during cache startup. However, some
global components are only created "on-demand", because a cache component
depends on them, and this can happen if someone uses getComponent instead of
getOrCreateComponent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: