Hello!
I suggest filing a ticket against Apache Ignite JIRA about that problem.
Regards,
--
Ilya Kasnacheev
вт, 9 апр. 2019 г. в 18:18, kresimir.horvat :
> Hi,
>
> solution you have suggested does work. So setting JMX_MON= before calling
> control.sh will run script without exception.
>
Hi,
solution you have suggested does work. So setting JMX_MON= before calling
control.sh will run script without exception.
Starting docker with NOJMX=1 and NOJMXI=1 doesn't. I found that
/docker/apache-ignite/run.sh script will start ignite.sh without -nojmx all
the time. If ignite.sh is started
Hello!
Have you tried it? Does it work?
Regards,
--
Ilya Kasnacheev
пн, 8 апр. 2019 г. в 14:31, kresimir.horvat :
> Hi,
>
> thank you for your replay. I will try solution you suggested.
>
> If I want to avoid modifications and commits of changes in docker container
> I will have to do the
Hi,
thank you for your replay. I will try solution you suggested.
If I want to avoid modifications and commits of changes in docker container
I will have to do the following:
1. start container with JMX_MON specified so ignite will start with open JMX
ports
2. pass NOJMX = 1 (ignite.sh) and
Hello!
Why won't you override it when starting control.sh? Like
% JMX_MON= bin/control.sh --activate
Regards,
--
Ilya Kasnacheev
пт, 5 апр. 2019 г. в 13:33, kresimir.horvat :
> Hi,
>
> I have problem with running control.sh scripts when using Apache Ignite in
> docker container.
> At first I
