[
https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331151#comment-16331151
]
Kirk Lund commented on GEODE-3554:
----------------------------------
I think a feature request just as this should focus on either 1) document not
invoking CacheFactory.getAnyInstance() from user callbacks OR 2) change
CacheFactory.getAnyInstance() so that it's safe to invoke from user callbacks,
but not both.
As for #2, the current plan is to deprecate and remove
CacheFactory.getAnyInstance(), so I don't think it's a good idea to accept a
feature request to make any behavior changes to this API.
I'd like to change this feature request to be documentation and javadocs
changes only.
> Fix startup freeze at callback to CacheFactory.getAnyInstance()
> -----------------------------------------------------------------
>
> Key: GEODE-3554
> URL: https://issues.apache.org/jira/browse/GEODE-3554
> Project: Geode
> Issue Type: New Feature
> Components: core
> Reporter: Fred Krone
> Priority: Major
> Labels: cache, geode-150
>
> As long as the product continues to invoke user plug-in callbacks during
> startup (and with the main thread), we probably need to document a warning
> not to use CacheFactory.getAnyInstance() as the API call is common in
> plug-ins and this will freeze startup.
> A better fix could be to make changes to cache initialization that would
> prevent this deadlock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
