[UIMA-3544] Refactor DUCC JmxAgent to allow daemon to start on jmx failure

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.0-Ducc
• Component/s: DUCC
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 13/Jan/14 19:09
• Updated: 13/Jan/14 19:39
• Resolved: 13/Jan/14 19:39

Description

Modify common code in AbstractDuccComponent that enables JMX for the DUCC daemon. Currently, when there is a failure binding a port to JMX service connector, the code keeps retrying with the next available port.

The bug here is that there are two distinct steps wrapped by a single try catch block. Improve this by wrapping try catch around getting a valid port, and a second try catch around code that binds the Jmx Service Connector to the port.

If the first step fails (getting valid port), the code retries until a valid port is found. If the second step fails (bind), the code should log a message stating the JMX is not available and return empty string for jmx URL. The daemon should continue initializing despite the fact the JMX is not available