You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Alex Dettinger (JIRA)" <ji...@apache.org> on 2019/07/02 11:54:00 UTC
[jira] [Resolved] (CAMEL-13713) Two CI server failures for
camel-ribbon
[ https://issues.apache.org/jira/browse/CAMEL-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Dettinger resolved CAMEL-13713.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0.M4
Two test classes were impacted:
ConsulDefaultServiceCallRouteTest
ConsulRibbonServiceCallRouteTest
This issue did not appear anymore in the last build, yet I've switched to dynamic port allocation in order to narrow down the probability of port conflict.
> Two CI server failures for camel-ribbon
> ---------------------------------------
>
> Key: CAMEL-13713
> URL: https://issues.apache.org/jira/browse/CAMEL-13713
> Project: Camel
> Issue Type: Task
> Components: tests
> Affects Versions: 3.0.0-M3
> Reporter: Claus Ibsen
> Assignee: Alex Dettinger
> Priority: Major
> Fix For: 3.0.0.M4
>
>
> Error Message
> java.io.IOException: Failed to bind to /127.0.0.1:8084
> Stacktrace
> org.apache.camel.RuntimeCamelException: java.io.IOException: Failed to bind to /127.0.0.1:8084
> Caused by: java.io.IOException: Failed to bind to /127.0.0.1:8084
> Caused by: java.net.BindException: Address already in use
> https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.consul.cloud/ConsulRibbonServiceCallRouteTest/testServiceCall/
> Has been failing for the last 5 builds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)