[jira] [Updated] (IGNITE-13479) Both ignite.sh and control.sh use the same JVM_OPTS. Control.sh doesn't start if JMX port was set

["Yaroslav Molochkov (Jira)" <ji...@apache.org>]

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

Yaroslav Molochkov updated IGNITE-13479:
----------------------------------------
    Fix Version/s: 2.9.1

> Both ignite.sh and control.sh use the same JVM_OPTS. Control.sh doesn't start if JMX port was set
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13479
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13479
>             Project: Ignite
>          Issue Type: Bug
>          Components: control.sh
>    Affects Versions: 2.8.1
>            Reporter: Semyon Danilov
>            Assignee: Semyon Danilov
>            Priority: Major
>              Labels: 2.9.1-rc
>             Fix For: 2.10, 2.9.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There is no other way to set parameters for docker images, so, when you set JMX port to JVM_OPTS, you can't start control.sh:
>  
> Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 49112; nested exception is:
> java.net.BindException: Address in use (Bind failed)
> sun.management.AgentConfigurationError: java.rmi.server.ExportException: Port already in use: 49112; nested exception is:
> java.net.BindException: Address in use (Bind failed)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)