[IGNITE-5730] .NET: Failed to load ignite.jni.dll when starting up multiple nodes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.3
• Component/s: platforms
• Labels: .NET
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 11/Jul/17 13:23
• Updated: 27/Sep/17 11:59
• Resolved: 27/Sep/17 09:21

Description

When starting multiple nodes at once (with a script of some kind), failure to load unmanaged dll can occur:

set IGNITE_NATIVE_TEST_CLASSPATH=true

FOR /L %%A IN (1,1,20) DO (
  start Apache.Ignite.exe
)

Exception:

ERROR: System.TypeInitializationException: The type initializer for 'Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils' threw an exception. ---> Apache.Ignite.Core.Common.IgniteException: Failed to load ignite.jni.dll: 126
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils..cctor()
   --- End of inner exception stack trace ---
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Initialize()
   at Apache.Ignite.Core.Impl.IgniteUtils.LoadDlls(String configJvmDllPath, ILogger log)
   at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
   at Apache.Ignite.IgniteRunner.Main(String[] args)

Error codes may be 5 (ERROR_ACCESS_DENIED) or 126 (ERROR_MOD_NOT_FOUND).

Issue Links

• relates to: IGNITE-5343 .NET: Interoperate with JVM directly, get rid of C++ layer
• links to: GitHub Pull Request #2755
• links to: TeamCity