[
https://issues.apache.org/jira/browse/IGNITE-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563188#comment-14563188
]
Vasilisa Sidorova commented on IGNITE-834:
------------------------------------------
I couldn't find the instrument to effectively verify this fix.
So I've try to reproduce this issue for the old build (before fix - released
community build 1.0.2) and for the new build (after fix - released community
build 1.0.5) by the next scenario:
1) Compile examples;
2) For 9 examples from
examples/src/main/java/org/apache/ignite/examples/datagrid: add cache.clear()
invoking into try-block where cache is created
3) Run two ExampleNodeStartup
4) Run all examples one by one starting next example don't waiting while
previous example is finished
So this way help to verify that only expected runtime exceptions are
reproducible for both builds. And 2 NPE modes from old build isn't reproducible
for new build
> IgniteCache.clearAll() throws NPE.
> ----------------------------------
>
> Key: IGNITE-834
> URL: https://issues.apache.org/jira/browse/IGNITE-834
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-2
> Reporter: Vladimir Ozerov
> Assignee: Vasilisa Sidorova
> Priority: Critical
> Fix For: sprint-5
>
>
> 1) Define XML configuration with a cache.
> 2) Start dedicated node.
> 3) Start another node programmatically and execute IgniteCache.clearAll().
> 4) With pretty high probabolity you will see NPE originating from
> GrdiCacheAdapter.GlobalClearAllCallable.call().
> Reason for this NPE is null returned from IgniteEx.cachex(). And this is not
> even a dynamically started cache, this is a cache defined in config and
> initialized on startup.
> If any other cache operation occurrs before "clearAll", no exception is
> thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
