Hi This is a well known barrier for irritation.
The camel-ftp had particiluar this issue on other platforms such as AIX, and some unix flavors. What we did to remedy this was to use a new number when unit testing to avoid clashing. I am wondering if we should do the same for - camel-jetty - camel-cxf That can have this issue as well sometimes, eg as port 9080, 8080, or what we use can cause the port number already in use issue. For inspiration see the camel-ftp there is some base ftp unit test classes that set ups the feature to use a new number each time. Any thoughts? -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
