-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Platform: PC, OS: Windows XP
I downloaded the latest Hudson, but my project won't build with it. This is the
console output from the build:
started
[vigilog] $ "C:\Program Files\Java\jdk1.6.0_01\jre\bin\java" cp "C:\apache
tomcat-6.0.10\webapps\hudson\WEB-INF\lib\maven-agent-1.103.jar;C:\Program
Files\Apache Software Foundation\maven-2.0.6\boot\classworlds-1.1.jar"
hudson.maven.agent.Main "C:\Program Files\Apache Software Foundation\maven-
2.0.6" C:\apache-tomcat-6.0.10\webapps\hudson\WEB-INF\lib\remoting-1.103.jar
C:\apache-tomcat-6.0.10\webapps\hudson\WEB-INF\lib\maven-interceptor-1.103.jar
channel started
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building Vigilog
[INFO] task-segment: [package]
[INFO] ----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://repo1.maven.org/maven2/org/jdesktop/animation/timing/timingframework/0.5/timingframework-0.5.pom
The downloading line is the last and it stayed that way for several minutes. I
then did "prepare for shutdown", which added this to the console output:
FATAL: null
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at hudson.remoting.Request.call(Request.java:81)
at hudson.remoting.Channel.call(Channel.java
:240)
at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:261)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:121)
at hudson.model.Run.run(Run.java:559)
at hudson.maven.MavenBuild.run
(MavenBuild.java:124)
at hudson.model.Executor.run(Executor.java:61)
Any idea what might be wrong? You can try to build my project if you want, it is
open source, the svn url is
https://vigilog.svn.sourceforge.net/svnroot/vigilog/trunk
and the maven target I used was 'package'
- duplicates
-
-
- Closed
-
[JENKINS-495] Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6
magnayn
added a comment - I'm now seeing this as well, with Tomcat 5.5 and maven 2.0.5;
It was working really nicely for me; I suspected a JDK update (1.6.0_01), but
downgrading JAVA_HOME to a 1.5 JDK didn't seem to make any difference.
Seems very odd as it was working very happily.
magnayn
added a comment - I'm now seeing this as well, with Tomcat 5.5 and maven 2.0.5;
It was working really nicely for me; I suspected a JDK update (1.6.0_01), but
downgrading JAVA_HOME to a 1.5 JDK didn't seem to make any difference.
Seems very odd as it was working very happily. 
jonin
added a comment - Created an attachment (id=60)
The Maven settings seem to be somehow broke; 'install' makes two installations: first in the cottect place and then under <userprofile>/.m2/repository (see attachment). I have internet access through proxy only, and have this same problem, could it be the cause?
jonin
added a comment - Created an attachment (id=60)
The Maven settings seem to be somehow broke; 'install' makes two installations: first in the cottect place and then under <userprofile>/.m2/repository (see attachment). I have internet access through proxy only, and have this same problem, could it be the cause? Probe is implemented in recent version of Hudson so that we can dump the call
stack of all threads. I now have an environment to reproduce this, yet I still
can't figure out what's going wrong.
So if anyone is experiencing the same problem, please try "Monitor Maven
Process" and get a thread dump for us.
When I get a stack dump, I see that Maven is hanging in reading from a stream,
so it's not like there's a deadlock going on or anything.
I was then playing with Process Explorer to see the call stack of native
threads, then I noticed that Maven came back to life and completed the whole build.
So still investigating this issue. Any information, even just "I have the same
problem in such and such environment", would be greatly appreciated.
I only see this on Windows systems. Is that be true with everyone?
I believe this is eventually reported again as issue #1458 and fixed in 1.219.
-
-
- This issue has been marked as a duplicate of 1458 ***
-
I'll need to implement a probe in the maven process so that we can obtain the
thread dump.