[
https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083718#comment-16083718
]
Yevgeniy Ignatyev commented on IGNITE-5123:
-------------------------------------------
The problem seems to be because PluginProvider#onIgniteStart is actually called
before internal components #onKernalStart callbacks are executed, contrarwise
to the javadoc of #onIgniteStart, the solution seems to simply move
PluginProvider notification after internal components callbacks.
> Ignite.cache(String) returns null in PluginProvider.onIgniteStart()
> -------------------------------------------------------------------
>
> Key: IGNITE-5123
> URL: https://issues.apache.org/jira/browse/IGNITE-5123
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Nick Pordash
> Assignee: Yevgeniy Ignatyev
> Attachments: ignite-plugin-failure.zip
>
>
> Given an Ignite node that has pre-configured caches (via
> IgniteConfiguration.setCacheConfiguration) if you try to obtain a reference
> to the cache instance in PluginProvider.onIgniteStart() you'll get a null
> reference.
> @Override
> public void onIgniteStart() throws IgniteCheckedException {
> ignite.cacheNames().forEach(name -> {
> assert ignite.cache(name) != null : "Cache is null: " + name;
> });
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
