[
https://issues.apache.org/jira/browse/CAMEL-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439710#comment-13439710
]
David Valeri commented on CAMEL-4814:
-------------------------------------
I removed the features.xml file from the cxf example and updated the README to
remove references to deploying in OSGi.
I checked the main features.xml file for Camel and the examples do not appear
to be listed in that file. A number of the examples contain their own
features.xml file and attach them to the build, but I do not see a feature file
that aggregates the multiple examples into one file.
I ran the camel-example-loan-broker example and verified that the ports are
being chosen dynamically in the test. Any failure in the past was likely a
random port collision that is unavoidable. The build history is unavailable in
Jenkins and the test seems to be passing in the current build.
I'm working through the remaining tests looking for static port usage.
> Use dynamic port numbers for unit tests the examples
> ----------------------------------------------------
>
> Key: CAMEL-4814
> URL: https://issues.apache.org/jira/browse/CAMEL-4814
> Project: Camel
> Issue Type: Task
> Components: examples
> Reporter: Claus Ibsen
> Assignee: David Valeri
> Fix For: 2.11.0
>
>
> Its a bit annoying that CI servers and whatnot fail tests due to a port
> number in use issue when testing the examples.
> > org.apache.cxf.interceptor.Fault: Could not start Jetty server on port
> > 9,000: Address already in use
> We should use dynamic port numbers, like we do when testing components.
> camel-test has a util class to find a free port number.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
