[
https://issues.jenkins-ci.org/browse/JENKINS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158844#comment-158844
]
David Dossot commented on JENKINS-3273:
---------------------------------------
Same problem here with Jenkins 1.449:
{code}
Started by an SCM change
Building in workspace /home/jenkins/jobs/rsb-public/workspace
Checkout:workspace / /home/jenkins/jobs/rsb-public/workspace -
hudson.remoting.LocalChannel@36b4fec5
Using strategy: Default
Checkout:workspace / /home/jenkins/jobs/rsb-public/workspace -
hudson.remoting.LocalChannel@36b4fec5
Fetching changes from 1 remote Git repository
Fetching upstream changes from *****
Seen branch in repository origin/HEAD
Seen branch in repository origin/master
Commencing build of Revision a3e51b8864cba056876bcd2e9144b17232e24885
(origin/HEAD, origin/master)
Checking out Revision a3e51b8864cba056876bcd2e9144b17232e24885 (origin/HEAD,
origin/master)
No change to record in branch origin/HEAD
No change to record in branch origin/master
Parsing POMs
[workspace] $ /home/jenkins/tools/JDK_1.6/bin/java -cp
/home/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/tools/Maven_3/boot/plexus-classworlds-2.4.jar
org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/tools/Maven_3
/var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.12.jar
/home/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 56845
ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
at java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
at java.net.ServerSocket.implAccept(ServerSocket.java:470)
at java.net.ServerSocket.accept(ServerSocket.java:438)
at
hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept(AbstractMavenProcessFactory.java:171)
at
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:227)
at hudson.maven.ProcessCache.get(ProcessCache.java:231)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:708)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Finished: ABORTED
{code}
> Maven build aborted before execution due to SocketTimeoutException
> ------------------------------------------------------------------
>
> Key: JENKINS-3273
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3273
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Platform: All, OS: Linux
> Reporter: peterandersen
> Assignee: ashlux
>
> Hi
> I have a build server that sometime abort the scheduled build with just error
> aborted - else no error messages, see example build log below.
> I have configured a logger for the fine level (logger: hudson, log level:
> fine)
> see catelina log below - no useful errors
> I have just start calling maven with -X for debug output - if maven was the
> course - but have not yet capture the error (if maven is to blame - don't
> think so)
> Any suggestions - please see logs are version data below
> Best regards
> Peter Andersen
> ------------
> Versions:
> Hudson: 1.289
> Tomcat: 6.0.18
> java version "1.6.0_0"
> OpenJDK Runtime Environment (build 1.6.0_0-b11)
> OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Maven: 2.0.9
> OS Debian 5, uname -a:
> Linux hudson 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
> GNU/Linux
>
> Example aborted build:
> started
> Updating svn://svn.lenio.dk/xxxx/trunk
> U ...
> A build.xml
> At revision 11963
> Parsing POMs
> [trunk] $ /usr/lib/jvm/java-6-openjdk/bin/java -Xmx768m -XX:MaxPermSize=256m
> -cp
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-agent-1.289.jar:/usr/share/maven2/boot/classworlds.jar
> hudson.maven.agent.Main /usr/share/maven2
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/remoting-1.289.jar
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-interceptor-1.289.jar
> 38194
> ERROR: Aborted
> No emails were triggered.
> finished: ABORTED
> Catalina log snippet
> Mar 11, 2009 1:33:35 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11, 2009 1:33:40 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11, 2009 1:33:45 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11, 2009 1:33:48 AM hudson.model.Run setResult
> FINE: diop-site-build #12 : result is set to ABORTED by
> hudson.model.Run.run(Run.java:896)
> Mar 11, 2009 1:33:48 AM hudson.model.Run run
> INFO: diop-site-build #12 main build action completed: ABORTED
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
