[
https://issues.apache.org/jira/browse/BROOKLYN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229979#comment-14229979
]
ASF GitHub Bot commented on BROOKLYN-98:
----------------------------------------
Github user grkvlt commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/369#issuecomment-65090782
:frog: Merging.
> Deploying JBoss6Server to AWS fails: jmx port not open
> ------------------------------------------------------
>
> Key: BROOKLYN-98
> URL: https://issues.apache.org/jira/browse/BROOKLYN-98
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.7.0-SNAPSHOT
> Reporter: Aled Sage
> Assignee: Aled Sage
>
> A customer reported failure when deploying JBoss6Server to aws-ec2 (timeout
> waiting for service up to be true).
> The `jmx.service.url` is
> `service:jmx:jmxmp://ec2-54-145-128-228.compute-1.amazonaws.com:31002` (note
> this is *not* port 31001).
> The entity also shows the fields:
> `jmx.direct.port.legacy.NOT_USED` on port `31001`
> `jmx.direct.port` on port `31002`.
> The aws security group only opened 31001.
> The problem is caused by the two `PortAttributeSensorAndConfigKey` in
> `UsesJmx` both pointing at `31001+`. When creating the VM, it only opens the
> first port in that range (i.e. 31001). However, when actually allocating
> values to the sensors the first gets 31001 and the second gets 31002. It may
> be a race which sensor gets which value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
