[
https://issues.apache.org/jira/browse/BROOKLYN-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943528#comment-14943528
]
Duncan Grant commented on BROOKLYN-179:
---------------------------------------
This also affects config values of 0 (and presumably -ve integers)
> 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)
