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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.10, 2.9.1
• Component/s: control.sh
• Labels: 2.9.1-rc
• Release Note: Replace JVM_OPTS in control.(sh|bat) with CONTROL_JVM_OPTS
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Semyon Danilov
• Reporter: Semyon Danilov
• Reviewer: Sergey Chugunov
• Created: 23/Sep/20 10:53
• Updated: 03/Nov/20 15:10
• Resolved: 02/Oct/20 12:14

Description

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)

Issue Links

• links to: GitHub Pull Request #8275