You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/09/06 17:24:00 UTC

[jira] [Updated] (GEODE-3554) Fix startup freeze at callback to CacheFactory.getAnyInstance()

     [ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Krone updated GEODE-3554:
------------------------------
    Description: 
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.



  was:
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.




> Fix startup freeze at callback to CacheFactory.getAnyInstance()  
> -----------------------------------------------------------------
>
>                 Key: GEODE-3554
>                 URL: https://issues.apache.org/jira/browse/GEODE-3554
>             Project: Geode
>          Issue Type: Improvement
>          Components: core
>            Reporter: Fred Krone
>
> 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
(v6.4.14#64029)