Jerry Cwiklik created UIMA-3544:
-----------------------------------

             Summary: Refactor DUCC JmxAgent to allow daemon to start on jmx 
failure
                 Key: UIMA-3544
                 URL: https://issues.apache.org/jira/browse/UIMA-3544
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: 1.0-Ducc


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



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to