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

Posted to user@ignite.apache.org by dwtrosii1 <da...@hexagonsi.com> on 2018/05/07 21:19:32 UTC

Setting JvmDllPath in Ignite 2.3.0

When setting the JvmDllPath in Ignite 2.3.0 in a configuration and starting
an ignite instance passing in that configuration, it does not seem to
register. The exception that is occurring is "Cannot load jvm.dll. Please
specify IgniteConfiguration.JvmDllPath or JAVA_HOME." I reviewed the source
code and it seems that a new ignite configuration is being created from the
source ignite configuration, in which the JvmDllPath property is not being
copied in the new configuration. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Setting JvmDllPath in Ignite 2.3.0

Posted by dwtrosii1 <da...@hexagonsi.com>.

Yes the source code file was IgniteConfiguration.cs in CopyLocalProperties. I
will upgrade to Ignite 2.4.0.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Setting JvmDllPath in Ignite 2.3.0

Posted by akurbanov <an...@gmail.com>.

Hi,

Can you specify the source code file where JvmDllPath is missed? If it's
IgniteConfiguration.cs/CopyLocalProperties, then the issue is fixed in
Ignite 2.4 with https://issues.apache.org/jira/browse/IGNITE-2662.

Best regards,
Anton



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/