[
https://issues.apache.org/jira/browse/IGNITE-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192146#comment-17192146
]
Ilya Kasnacheev commented on IGNITE-13404:
------------------------------------------
It seems to no longer set file.encoding for control.sh and sqlline.sh.
Maybe we can just put -Dfile.encoding into JVM_XOPTS instead of JVM_OPTS? Plus
we need to make use of JVM_XOPTS in sqlline.sh. WDYT [~sdarlington]?
> ignite.sh fails to set default JVM parameters
> ---------------------------------------------
>
> Key: IGNITE-13404
> URL: https://issues.apache.org/jira/browse/IGNITE-13404
> Project: Ignite
> Issue Type: Bug
> Environment: Anything but Windows.
> Reporter: Stephen Darlington
> Assignee: Stephen Darlington
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ignite.sh [tries to set parameters for the
> JVM|https://github.com/apache/ignite/blob/master/bin/ignite.sh#L102] if
> they've not been set by the user (defaulting to 1Gb heap), unfortunately,
> it's always set by an earlier part of the startup scripts.
> Conversely, ignitevisorcmd.sh always sets the same parameters, even if they
> have already been set by the user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
