| Summary: | virgo.kernel.snapshot build is unstable on hudson-slave2 and is OK on hudson-slave1 | ||
|---|---|---|---|
| Product: | Community | Reporter: | violeta.georgieva |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | violeta.georgieva |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
violeta.georgieva
Based on this line in your log:
[junit] Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9875; nested exception is:
[junit] java.net.BindException: Address already in use
I went digging on slave2 and found the following process:
55011 22585 1 0 Feb09 ? 00:05:46 /opt/public/common/sun-jdk1.6.0_21_x64/jre/bin/java -Dcom.sun.management.jmxremote.port=9875 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.login.config=virgo-kernel -Dcom.sun.management.jmxremote.access.file=/opt/users/hudsonbuild/workspace/virgo.kernel.snapshot/org.eclipse.virgo.kernel.smoketest/target/test-expanded/virgo-kernel-3.0.0.CI-2011-02-09_08-01-37/config/org.eclipse.virgo.kernel.jmxremote.access.properties -Djavax.net.ssl.keyStore=/opt/users/hudsonbuild/workspace/virgo.kernel.snapshot/org.eclipse.virgo.kernel.smoketest/target/test-expanded/virgo-kernel-3.0.0.CI-2011-02-09_08-01-37/config/keystore (snip)
So I suspect that one of your previous builds started this process, and then failed to kill it, and so it's been blocking runs on that slave.
I've killed the job so let me know if the problem persists.
This is the first job I've ever seen with a parameter list so long that ps -aef can't display it all.
-M.
Thanks! |