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

Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2022/09/09 16:34:00 UTC

[jira] [Updated] (IGNITE-17432) ignitevisorcmd can't run in jdk17 env

     [ https://issues.apache.org/jira/browse/IGNITE-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Pavlov updated IGNITE-17432:
-----------------------------------
    Release Note: Fixed the run of ignitevisorcmd in JDK 17 environmen  (was: Fixed run ignitevisorcmd in JDK 17 environment)

> ignitevisorcmd can't run in jdk17 env
> -------------------------------------
>
>                 Key: IGNITE-17432
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17432
>             Project: Ignite
>          Issue Type: Bug
>          Components: cli
>    Affects Versions: 2.13
>            Reporter: YuJue Li
>            Assignee: YuJue Li
>            Priority: Minor
>             Fix For: 2.14
>
>         Attachments: 0001-IGNITE-17432-ignitevisorcmd-can-t-run-in-jdk17-env.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Unrecognized VM option 'MaxPermSize=128M' 
> Error: Could not create the Java Virtual Machine. 
> Error: A fatal exception has occurred. Program will exit.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)