ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: Some problem with execution ignite.bat in master
Date Thu, 27 Dec 2018 18:22:21 GMT
Ilya,

Why do we use -J in general? Is it used to pass a specific type of
parameters? I know -D or - X but can't recall what -J is supposed to be
used for.

--
Denis


On Thu, Dec 27, 2018 at 6:34 AM Ilya Kasnacheev <ilya.kasnacheev@gmail.com>
wrote:

> Hello!
>
> I have debugged this issue. It seems to be a JVM bug on Windows, where JVM
> will silently fail to run program's main class:
>
> java HelloWorld -v -J1 -J2 - works
> java HelloWorld -v -J1 -J2 -J3 - fails
> java -Dfile.encoding=UTF-8 HelloWorld -v -J1 -J2 -J3 - works
> java -Dfile.encoding=UTF-8 HelloWorld -v -J1 -J2 -J3 -J4 - fails
>
> It seems to be fixed on Java 11.
>
> I don't think we should fix it (and can close the issue), but if we really
> wanted we could replace -J with, let's say, -W
> java HelloWorld -v -W1 -W2 -W3 -W4 works.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 27 авг. 2018 г. в 11:33, Anton Vinogradov <av@apache.org>:
>
> > Dmitry,
> > Not sure I understand the issue, but I see no reason to rollback
> anything.
> > In case we have some issues, let's just fix them.
> >
> > сб, 25 авг. 2018 г. в 0:53, Dmitriy Pavlov <dpavlov.spb@gmail.com>:
> >
> > > Hi Anton,
> > >
> > > Do you have objections about a partial rollback of changes?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пт, 24 авг. 2018 г. в 14:24, ARomantsov <ArtRomMar@gmail.com>:
> > >
> > >> Hello, Igniters.
> > >>
> > >> I'm testing some java keys with ignite.bat and notice that using more
> > that
> > >> four keys lead to internal problem and ignite.bat ignoring them all.
> > >>
> > >> So I created issue https://issues.apache.org/jira/browse/IGNITE-8837
> > and
> > >> investigated , below what i founded
> > >>
> > >> 1) inside file ignite.bat happen call bin/include/parseargs.bat with
> > next
> > >> code to parse arguments
> > >> set convertArgsCmd="!JAVA_HOME!\bin\java.exe" -cp "%CP%"
> > >> org.apache.ignite.startup.cmdline.CommandLineTransformer %*
> > >>
> > >> 2) call of org.apache.ignite.startup.cmdline.CommandLineTransformer
> > >> correct
> > >> parsing JVM arguments only if they count less five
> > >>
> > >> 3) This problem (2) easy fix by add to set in convertArgsCmd one of
> next
> > >> Java key ( -Dfile.encoding=IBM866 or -Dfile.encoding=UTF-8)
> > >>
> > >> 4) Like part of issue
> https://issues.apache.org/jira/browse/IGNITE-7135
> > >> it
> > >> already had fix (3) and included in Ignite 2.4
> > >>
> > >> 5) Unfortunately, when fix issue
> > >> https://issues.apache.org/jira/browse/IGNITE-898 that key was removed
> > >> and
> > >> that lead to problem in 2.5 , 2.6, master
> > >>
> > >> What correct steps to back ignite.bat working correct on windows in
> > >> master /
> > >> 2.7? Both of ticket in (4) / (5) fix another problems , is correct to
> > >> reopen
> > >> one of them?
> > >>
> > >>
> > >>
> > >> --
> > >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >>
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message