[
https://issues.apache.org/jira/browse/BROOKLYN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229821#comment-14229821
]
ASF GitHub Bot commented on BROOKLYN-98:
----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/369
Fix BROOKLYN-98: jmx.direct.port opened in security group
- Fixes JBoss6Server deploying to aws-ec2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/incubator-brooklyn
fix/UsesJmx-port-allocation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/369.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #369
----
commit 3b7f0f3681cbefe683fbd208a2e4656055e60254
Author: Aled Sage <[email protected]>
Date: 2014-12-01T14:11:25Z
Fix BROOKLYN-98: jmx.direct.port opened in security group
- Fixes JBoss6Server deploying to aws-ec2
----
> 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)
