[ 
https://issues.apache.org/jira/browse/IGNITE-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205468#comment-17205468
 ] 

Ignite TC Bot commented on IGNITE-13479:
----------------------------------------

{panel:title=Branch: [pull/8275/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8275/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5628460&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>             Fix For: 2.10
>
>          Time Spent: 20m
>  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)

Reply via email to