It sometimes fails in running the Maven2 project build, which often goes well by
trying again. We get the following error messages.

[Beckmann] $ C:\Bin\Java\1.5.0_15/bin/java -Dmaven.test.skip=true -Xmx1024m -cp
C:\Bin\Tomcat\6.0-v2\webapps\hudson\WEB-INF\lib\maven-agent-1.252.jar;C:\Bin\Maven\2.0.9\boot\classworlds-1.1.jar
hudson.maven.agent.Main C:\Bin\Maven\2.0.9
C:\Bin\Tomcat\6.0-v2\webapps\hudson\WEB-INF\lib\remoting-1.252.jar
C:\Bin\Tomcat\6.0-v2\webapps\hudson\WEB-INF\lib\maven-interceptor-1.252.jar 4004
ERROR: Failed to parse POMs
java.net.SocketTimeoutException: Accept timed out
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
at java.net.ServerSocket.implAccept(ServerSocket.java:453)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at
hudson.maven.MavenProcessFactory$SocketHandler$AcceptorImpl.accept(MavenProcessFactory.java:142)
at hudson.maven.MavenProcessFactory.newProcess(MavenProcessFactory.java:175)
at hudson.maven.ProcessCache.get(ProcessCache.java:170)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:329)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:240)
at hudson.model.Run.run(Run.java:793)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:205)
at hudson.model.ResourceController.execute(ResourceController.java:70)
at hudson.model.Executor.run(Executor.java:88)
finished: FAILURE