[IGNITE-8404] NPE when shutting down non-initialized mapped file memory provier

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5
• Assignee: Alexey Goncharuk
• Reporter: Alexey Goncharuk
• Created: 26/Apr/18 16:29
• Updated: 26/Apr/18 17:11
• Resolved: 26/Apr/18 17:11

Description

If a node has mapped file memory provider and node initialization fails, I get the following exception:

java.lang.NullPointerException
    at org.apache.ignite.internal.mem.file.MappedFileMemoryProvider.shutdown(MappedFileMemoryProvider.java:97)
    at org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.stop(PageMemoryNoStoreImpl.java:239)
    at org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.stop0(IgniteCacheDatabaseSharedManager.java:649)
    at org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.stop(GridCacheSharedManagerAdapter.java:94)
    at org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:888)
    at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2109)
    at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1987)
    at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1074)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
    at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
    at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
    at org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1062)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:948)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:717)
    at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:686)
    at org.apache.ignite.Ignition.start(Ignition.java:347)
    at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)

The cause is obvious - we try to access an uninitialized field.