You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/08 13:35:00 UTC
[jira] [Commented] (IGNITE-11999) .NET unable to specify JvmDllPath
for standalone node
[ https://issues.apache.org/jira/browse/IGNITE-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946883#comment-16946883 ]
Maxim Muzafarov commented on IGNITE-11999:
------------------------------------------
[~ashapkin]
Hello, any updates here? Should we move this issue to the next release?
> .NET unable to specify JvmDllPath for standalone node
> -----------------------------------------------------
>
> Key: IGNITE-11999
> URL: https://issues.apache.org/jira/browse/IGNITE-11999
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.7.5
> Reporter: Alexandr Shapkin
> Assignee: Alexandr Shapkin
> Priority: Minor
> Fix For: 2.8
>
>
> We have a -JvmDllPath CLI parameter/Ignite.JvmDllPath xml config for standalone nodes, that should take care about JVM dll location configuration.
> This parameter won't work since Apache.Ignite.Config.Configurator expects another one:
> /** Command line argument: Path to JVM dll. */
> private const string CmdJvmDll = "JvmDll";
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)