Re: Running control.sh in docker container when JXM is started

2019-04-09 Thread Ilya Kasnacheev 
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.
> 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 without -nojmx script parseargs.sh will
> override NOJMX=1 value I have passed as env variable.
> I had to change run.sh and commit new docker container.
>
> Is it possible to add support for -nojmx flag when running docker
> container?
>
> Regards,
> Kresimir
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Running control.sh in docker container when JXM is started

2019-04-09 Thread kresimir.horvat 
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 without -nojmx script parseargs.sh will
override NOJMX=1 value I have passed as env variable.
I had to change run.sh and commit new docker container.

Is it possible to add support for -nojmx flag when running docker container?

Regards,
Kresimir



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running control.sh in docker container when JXM is started

2019-04-09 Thread Ilya Kasnacheev 
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 following:
> 1. start container with JMX_MON specified so ignite will start with open
> JMX
> ports
> 2. pass NOJMX = 1 (ignite.sh) and NOJMXI = 1 (control.sh) so my JMX_MON
> won't be overridden by ignite.sh or control.sh
> 3. when starting control.sh manually pass empty JMX_MON and NOJMXI = 1
>
> Please correct me if I am wrong.
>
> Regards,
> Kresimir
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Running control.sh in docker container when JXM is started

2019-04-08 Thread 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 following:
1. start container with JMX_MON specified so ignite will start with open JMX
ports
2. pass NOJMX = 1 (ignite.sh) and NOJMXI = 1 (control.sh) so my JMX_MON
won't be overridden by ignite.sh or control.sh
3. when starting control.sh manually pass empty JMX_MON and NOJMXI = 1

Please correct me if I am wrong.

Regards,
Kresimir



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running control.sh in docker container when JXM is started

2019-04-05 Thread Ilya Kasnacheev 
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 was using solution we found for running ignite in docker and
> using JMX
>
> http://apache-ignite-users.70518.x6.nabble.com/JMX-port-for-Ignite-in-docker-td27491.html
> But when I invoke control.sh script with --state or any other parameres
> (--activate, --deactivate) I get error for port being used
> /sun.management.AgentConfigurationError: java.rmi.server.ExportException:
> Port already in use: 54321; nested exception is:
> java.net.BindException: Address in use (Bind failed)
> at
>
> sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:800)
> at
>
> sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:468)
> at sun.management.Agent.startAgent(Agent.java:262)
> at sun.management.Agent.startAgent(Agent.java:452)
> Caused by: java.rmi.server.ExportException: Port already in use: 54321;
> nested exception is:
> java.net.BindException: Address in use (Bind failed)
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)
> at
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)
> at
>
> sun.management.jmxremote.ConnectorBootstrap$PermanentExporter.exportObject(ConnectorBootstrap.java:199)
> at
>
> javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:146)
> at
>
> javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:122)
> at
>
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:404)
> at
>
> sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorBootstrap.java:796)
> ... 3 more
> Caused by: java.net.BindException: Address in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at java.net
> .AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at java.net.ServerSocket.(ServerSocket.java:237)
> at java.net.ServerSocket.(ServerSocket.java:128)
> at
>
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
> at
>
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345)
> at
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
> at
> sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)/
>
>
> I have tried lot of options for passing parameters and on the end I have
> removed call of findAvailableJmxPort from ignite.sh and control.sh scripts,
> and passed $JXM_MON when running docker container.
> Java process is started with all passed parameters and I can connect with
> VisualVm, but when using control.sh script problem with port remains.
>
> I assume problem is in $JMX_MON used for invocation of java process all the
> time.
> Can someone please check this?
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>