Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Wim Deblauwe
Hi,

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'

regards,

Wim


--
Vigilog - an open source log file viewer: http://vigilog.sourceforge.net
Blog: http://www.jroller.com/page/Fester
Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Kohsuke Kawaguchi
Administrator

Thanks. This is actually interesting, as we have some other user
reporting issues with Maven2.0.6 (but they didn't even get to this point.)

  1. can you try older versions of Maven, like 2.0.4? Does that make any
     difference?

  2. can you file this as an issue? I'll try it.

Wim Deblauwe wrote:

> Hi,
>
> 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'
>
> regards,
>
> Wim
>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Wim Deblauwe


2007/4/20, Kohsuke Kawaguchi <[hidden email]>:

Thanks. This is actually interesting, as we have some other user
reporting issues with Maven2.0.6 (but they didn't even get to this point.)

  1. can you try older versions of Maven, like 2.0.4? Does that make any
     difference?

Don't think that will make a difference, but I will try.

  2. can you file this as an issue? I'll try it.

Done: https://hudson.dev.java.net/issues/show_bug.cgi?id=495

I don't know if that helps, but Hudson reported the build as successfull in the console output of tomcat, however, according to the webinterface, it was still building.

If you want to try my project, you will need a settings.xml file and some additional jars in your local repository. Maybe you can try with a simple project first. Let me know if you need help to reproduce.

regards,

Wim

--
Vigilog - an open source log file viewer: http://vigilog.sourceforge.net
Blog: http://www.jroller.com/page/Fester
Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Kohsuke Kawaguchi
Administrator
Wim Deblauwe wrote:

> 2007/4/20, Kohsuke Kawaguchi <[hidden email]>:
>>
>>
>> Thanks. This is actually interesting, as we have some other user
>> reporting issues with Maven2.0.6 (but they didn't even get to this point.)
>>
>>   1. can you try older versions of Maven, like 2.0.4? Does that make any
>>      difference?
>
>
> Don't think that will make a difference, but I will try.
>
>   2. can you file this as an issue? I'll try it.
>
>
> Done: https://hudson.dev.java.net/issues/show_bug.cgi?id=495
>
> I don't know if that helps, but Hudson reported the build as successfull in
> the console output of tomcat, however, according to the webinterface, it was
> still building.
Is this now a different issue? That is, your original problem report was
that Maven get stuck at downloading a file.

For "hudson hanging after a build is done" issue, there are other things
we can check.

> If you want to try my project, you will need a settings.xml file and some
> additional jars in your local repository. Maybe you can try with a simple
> project first. Let me know if you need help to reproduce.

I do have a fair number of the m2 projects building at my production
installation of Hudson, so I don't think I can reproduce it by trying
something simple --- if that's the case I should have already seen it.

I'm thinking more in terms of what probes I can add to Hudson so that I
can get more information from your Hudson's execution.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Wim Deblauwe
Is this now a different issue? That is, your original problem report was
that Maven get stuck at downloading a file.

It is the same issue. Maven gets stuck at downloading the file, but the tomcat console prints that the build  was succesful. The webinterface still shows the spinning icon at the console output and the dot blinks indicating that the build is busy.

Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Victor Glushenkov-2
In reply to this post by Kohsuke Kawaguchi
Kohsuke Kawaguchi wrote:
>   1. can you try older versions of Maven, like 2.0.4? Does that make
> any difference?
I am facing the same problem with Maven 2.0.4. Hudson build stucks on
checking updates:
> [INFO] Scanning for projects...
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Common Runtime
> [INFO]    task-segment: [install]
> [INFO] ----------------------------------------------------------------------------
> [INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for updates from m2.java.net
I think it isn't related to Tomcat. I use Jetty (through Maven plugin)
to run Hudson war.
> I do have a fair number of the m2 projects building at my production
> installation of Hudson, so I don't think I can reproduce it by trying
> something simple --- if that's the case I should have already seen it.
>
> I'm thinking more in terms of what probes I can add to Hudson so that
> I can get more information from your Hudson's execution.
I will try to debug it in the near future.

--
Pharmanet, Cubus Team

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Kohsuke Kawaguchi
Administrator
Victor Glushenkov wrote:
>> I'm thinking more in terms of what probes I can add to Hudson so that
>> I can get more information from your Hudson's execution.
> I will try to debug it in the near future.

Thanks. I can't reproduce this problem so far, so your being able to
reproduce the issue is very helpful.

If you need to attach the debugger into the Maven process that Hudson
launches, you can do so by editing MavenBuild.debugPort static variable.

Or alternatively you can launch hudson like:

   java -Dudson.maven.MavenBuild.debugPort=5556 hudson.war

and every Maven process launched with Hudson will wait for remote
debugger at port 5556.

Hope that lets you see where things are stuck.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Nigel Magnay
Did anyone get to the bottom of this or have any pointers ?

I've been using hudson fine for ages and all of a sudden it seems to be doing exactly this for me. I've changed to 1.105, but I don't think it's that..

On 21/04/07, Kohsuke Kawaguchi <[hidden email]> wrote:
Victor Glushenkov wrote:
>> I'm thinking more in terms of what probes I can add to Hudson so that
>> I can get more information from your Hudson's execution.
> I will try to debug it in the near future.

Thanks. I can't reproduce this problem so far, so your being able to
reproduce the issue is very helpful.

If you need to attach the debugger into the Maven process that Hudson
launches, you can do so by editing MavenBuild.debugPort static variable.

Or alternatively you can launch hudson like:

   java -Dudson.maven.MavenBuild.debugPort=5556 hudson.war

and every Maven process launched with Hudson will wait for remote
debugger at port 5556.

Hope that lets you see where things are stuck.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Kohsuke Kawaguchi
Administrator
I first need to implement the probe point (scriting console and thread
dump to start with) so that people with this problem can get more
information for us.

Sounds like this is impacting a larger number of people, so I'll try
to work on it asap.

2007/4/30, Nigel Magnay <[hidden email]>:

> Did anyone get to the bottom of this or have any pointers ?
>
> I've been using hudson fine for ages and all of a sudden it seems to be
> doing exactly this for me. I've changed to 1.105, but I don't think it's
> that..
>
>
> On 21/04/07, Kohsuke Kawaguchi <[hidden email]> wrote:
> > Victor Glushenkov wrote:
> > >> I'm thinking more in terms of what probes I can add to Hudson so that
> > >> I can get more information from your Hudson's execution.
> > > I will try to debug it in the near future.
> >
> > Thanks. I can't reproduce this problem so far, so your being able to
> > reproduce the issue is very helpful.
> >
> > If you need to attach the debugger into the Maven process that Hudson
> > launches, you can do so by editing MavenBuild.debugPort static variable.
> >
> > Or alternatively you can launch hudson like:
> >
> >    java -Dudson.maven.MavenBuild.debugPort=5556
> hudson.war
> >
> > and every Maven process launched with Hudson will wait for remote
> > debugger at port 5556.
> >
> > Hope that lets you see where things are stuck.
> >
> > --
> > Kohsuke Kawaguchi
> > Sun Microsystems                   [hidden email]
> >
> >
>
>


--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Nigel Magnay
I'll add this to the bug, but I've got it working. My default environment uses tomcat through XAMPP on win 2003 server. When I log in as the tomcat user, set the JDK to a 1.5, and run tomcat from the console, it seems to work fine.

I'm suspicious of the JDK 1.6 01 update - my machine did update to that around about the time things started going awry.

On 30/04/07, Kohsuke Kawaguchi <[hidden email]> wrote:
I first need to implement the probe point (scriting console and thread
dump to start with) so that people with this problem can get more
information for us.

Sounds like this is impacting a larger number of people, so I'll try
to work on it asap.

2007/4/30, Nigel Magnay < [hidden email]>:

> Did anyone get to the bottom of this or have any pointers ?
>
> I've been using hudson fine for ages and all of a sudden it seems to be
> doing exactly this for me. I've changed to 1.105, but I don't think it's
> that..
>
>
> On 21/04/07, Kohsuke Kawaguchi <[hidden email]> wrote:
> > Victor Glushenkov wrote:
> > >> I'm thinking more in terms of what probes I can add to Hudson so that
> > >> I can get more information from your Hudson's execution.
> > > I will try to debug it in the near future.
> >
> > Thanks. I can't reproduce this problem so far, so your being able to
> > reproduce the issue is very helpful.
> >
> > If you need to attach the debugger into the Maven process that Hudson
> > launches, you can do so by editing MavenBuild.debugPort static variable.
> >
> > Or alternatively you can launch hudson like:
> >
> >    java -Dudson.maven.MavenBuild.debugPort=5556
> hudson.war
> >
> > and every Maven process launched with Hudson will wait for remote
> > debugger at port 5556.
> >
> > Hope that lets you see where things are stuck.
> >
> > --
> > Kohsuke Kawaguchi
> > Sun Microsystems                   [hidden email]
> >
> >
>
>


--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Builds hangs with Tomcat 6.0.10, JDK 1.6.0_01 and Maven 2.0.6

Kohsuke Kawaguchi
Administrator
OK. Thanks for the additional data.

2007/4/30, Nigel Magnay <[hidden email]>:

> I'll add this to the bug, but I've got it working. My default environment
> uses tomcat through XAMPP on win 2003 server. When I log in as the tomcat
> user, set the JDK to a 1.5, and run tomcat from the console, it seems to
> work fine.
>
> I'm suspicious of the JDK 1.6 01 update - my machine did update to that
> around about the time things started going awry.
>
>
> On 30/04/07, Kohsuke Kawaguchi <[hidden email]> wrote:
> >
> > I first need to implement the probe point (scriting console and thread
> > dump to start with) so that people with this problem can get more
> > information for us.
> >
> > Sounds like this is impacting a larger number of people, so I'll try
> > to work on it asap.
> >
> > 2007/4/30, Nigel Magnay < [hidden email]>:
> > > Did anyone get to the bottom of this or have any pointers ?
> > >
> > > I've been using hudson fine for ages and all of a sudden it seems to be
> > > doing exactly this for me. I've changed to 1.105, but I don't think it's
> > > that..
> > >
> > >
> > > On 21/04/07, Kohsuke Kawaguchi <[hidden email] > wrote:
> > > > Victor Glushenkov wrote:
> > > > >> I'm thinking more in terms of what probes I can add to Hudson so
> that
> > > > >> I can get more information from your Hudson's execution.
> > > > > I will try to debug it in the near future.
> > > >
> > > > Thanks. I can't reproduce this problem so far, so your being able to
> > > > reproduce the issue is very helpful.
> > > >
> > > > If you need to attach the debugger into the Maven process that Hudson
> > > > launches, you can do so by editing MavenBuild.debugPort static
> variable.
> > > >
> > > > Or alternatively you can launch hudson like:
> > > >
> > > >    java -Dudson.maven.MavenBuild.debugPort=5556
> > > hudson.war
> > > >
> > > > and every Maven process launched with Hudson will wait for remote
> > > > debugger at port 5556.
> > > >
> > > > Hope that lets you see where things are stuck.
> > > >
> > > > --
> > > > Kohsuke Kawaguchi
> > > > Sun Microsystems                   [hidden email]
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Kohsuke Kawaguchi
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]