You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/07/10 16:33:10 UTC
[jira] [Resolved] (INFRA-11694) Unable to open jmx ports for unit
tests in the build
[ https://issues.apache.org/jira/browse/INFRA-11694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambertus resolved INFRA-11694.
-------------------------------------
Resolution: Information Provided
Assignee: Chris Lambertus
> Unable to open jmx ports for unit tests in the build
> ----------------------------------------------------
>
> Key: INFRA-11694
> URL: https://issues.apache.org/jira/browse/INFRA-11694
> Project: Infrastructure
> Issue Type: Task
> Components: Jenkins
> Reporter: Navina Ramesh
> Assignee: Chris Lambertus
>
> I don't believe this is a bug. Perhaps a misconfiguration on my end.
> I setup a Multi-configuration project in Jenkins for building apache/samza on commit push. One of the unit test in the code base, creates a JmxServer at a random port and verifies that it has come up. While these tests pass fine on my local builds, it seems to fail on Jenkins with a "ConnectException: Connection refused to host: jenkins-beam1.apache.org"
> Is there anything in Jenkins that will disallow bringing up JmxServer in ephemeral ports? Should I configure something in my Jenkins project configuration?
> Sample build console output can be seen here - https://builds.apache.org/job/samza-build-post-commit/3/default/console
> Any feedback will be useful.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)