You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by "Duncan Grant (JIRA)" <ji...@apache.org> on 2015/10/05 17:30:28 UTC

[jira] [Created] (BROOKLYN-179) Brooklyn tries to open ports for all config values of type int

Duncan Grant created BROOKLYN-179:
-------------------------------------

             Summary: Brooklyn tries to open ports for all config values of type int
                 Key: BROOKLYN-179
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-179
             Project: Brooklyn
          Issue Type: Bug
            Reporter: Duncan Grant
             Fix For: 0.8.0


Described in the following PR https://github.com/apache/incubator-brooklyn/pull/870

Context: a relatively recent change meant that all config keys were searched for any type that can be coerced to a PortRange, which was then added to the set of "required open ports" by SoftwareProcessImpl. However, since type coercions also exist from integer/long/string, this resulted in spurious port values being added, and in at least one customer scenario, a runtime exception when a value >16 bits was incorrectly subsumed into the port set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)