Chris, If you can use tomcat maven plugin rather than jetty. It's possible to use port 0 (which means jvm will use the first available port). I don't know exactly what your build do so I cannot tell you if that's possible or not for your use case. But in Archiva project, we start an embeded tomcat running a war then run selenium tests. And we use port 0 so problem with reserved port !
2012/10/1 Brett Porter <[email protected]>: > Chris, > > This sounds like you've had some jobs hang that held on to the port, as it'd > be unlikely another project is using the same port. > > If you need to make sure you get distinct ports, try: > http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html > > Either way, if the builds are leaving processes around, that should be sorted > out. Someone with access to the particular Jenkins node you're building on > would have to answer that. > > - Brett > > On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" > <[email protected]> wrote: > >> Hey Martin, >> >> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml >> in Apache SIS to do automatic Jetty testing. I found this code snippet: >> >> {code} >> <execution> >> <id>start-jetty</id> >> <phase>pre-integration-test</phase> >> <goals> >> <goal>run</goal> >> </goals> >> <configuration> >> <connectors> >> <connector >> implementation="org.eclipse.jetty.server.nio.SelectChannelConnector"> >> <port>50234</port> >> </connector> >> </connectors> >> <stopPort>50500</stopPort> >> <scanIntervalSeconds>10</scanIntervalSeconds> >> <daemon>true</daemon> >> <systemProperties> >> <systemProperty> >> <name>org.apache.commons.logging.Log</name> >> <value>org.apache.commons.logging.impl.Jdk14Logger</value> >> </systemProperty> >> <systemProperty> >> <name>java.util.logging.config.file</name> >> <value>./src/test/resources/logging.properties</value> >> </systemProperty> >> </systemProperties> >> </configuration> >> </execution> >> >> {code} >> >> That I *thought* scans different ports and tries to find a free one on the >> machine. >> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong? >> Can someone help? :) >> >> Thanks! >> >> Cheers, >> Chris >> >> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote: >> >>> Hello Chris >>> >>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit : >>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035. >>>> Let's see if that fixes it. >>> >>> Thanks! But unfortunately, we still got a "java.net.BindException: Address >>> already in use" despite the new port number. I wonder if all ports have >>> been closed? >>> >>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? >>> They would still be executed on the developers local machine. >>> >>> Martin >>> >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > http://twitter.com/brettporter > > > > > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
