Hudson is clearly having problems. I'm fairly certain this has nothing to do with our build.
On Fri, Feb 5, 2010 at 5:03 PM, Apache Hudson Server <[email protected]> wrote: > See > <http://hudson.zones.apache.org/hudson/job/Shiro/org.apache.shiro$shiro-core/131/> > > ------------------------------------------ > Started by user lhazlewood > Building on master > $ /home/hudson/tools/java/latest1.5/bin/java -cp > /export/home/hudson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.338.jar:/home/hudson/tools/maven/latest/boot/classworlds-1.1.jar > hudson.maven.agent.Main /home/hudson/tools/maven/latest > /export/home/hudson/tools/tomcat/latest/webapps/hudson/WEB-INF/lib/remoting-1.338.jar > > /export/home/hudson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.338.jar > 34453 > /export/home/hudson/hudson/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar > FATAL: Accept timed out > 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:167) > at > hudson.maven.MavenProcessFactory.newProcess(MavenProcessFactory.java:202) > at hudson.maven.ProcessCache.get(ProcessCache.java:231) > at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:507) > at > hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417) > at hudson.model.Run.run(Run.java:1179) > at hudson.maven.MavenBuild.run(MavenBuild.java:200) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:122) > >
