issue with hudson 1.102

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

issue with hudson 1.102

Replogle, Andrew

Hello Hudson Users,

 

I picked up Hudson 1.102 to get the support for maven 2.0.6 and we’re running on RHES 3.x and no matter what I try and build I get the following error in the console:

 

started
[trunk] $ /usr/local/jdk1.5.0_05/jre/bin/java -cp /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-agent-1.102.jar:/usr/local/bsystem/m2/maven-2.0.6/core/boot/classworlds-1.1.jar hudson.maven.agent.Main /usr/local/bsystem/m2/maven-2.0.6 /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/remoting-1.102.jar /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-interceptor-1.102.jar
channel started
FATAL: null
hudson.util.IOException2
        at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:177)
        at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:136)
        at hudson.remoting.UserRequest.perform(UserRequest.java:57)
        at hudson.remoting.UserRequest.perform(UserRequest.java:22)
        at hudson.remoting.Request$2.run(Request.java:178)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at hudson.maven.agent.Main.launch(Main.java:70)
        at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:160)
        ... 7 more
Caused by: java.lang.IllegalStateException: The internal default plexus-bootstrap.xml is missing. This is highly irregular, your plexus JAR is most likely corrupt.
        at org.codehaus.plexus.DefaultPlexusContainer.initializeConfiguration(DefaultPlexusContainer.java:1062)
        at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:636)
        at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
        at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:156)
        ... 15 more

 

I’ve checked the md5sum of the war several times after downloading it to make sure the war wasn’t corrupt (a9f15d85c815c00d001029bcd6b8838d)

Unless Tomcat is corrupting a jar in the explosion process I don’t think this is a corruption issue.

 

Is this possibly related to the maven 2.0.6 support or is this a separate issue? Any assistance or direction is greatly appreciated. Thanks =]

 

Andrew

Reply | Threaded
Open this post in threaded view
|

Re: issue with hudson 1.102

Rhett Sutphin
Hi,

> I’ve checked the md5sum of the war several times after downloading  
> it to make sure the war wasn’t corrupt  
> (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don’t  
> think this is a corruption issue.
>
>
> Is this possibly related to the maven 2.0.6 support or is this a  
> separate issue? Any assistance or direction is greatly appreciated.  
> Thanks =]
I'm not 100% sure of this, but I think Hudson uses your locally-
installed maven, even with the native m2 support.  (You can see it in  
the command string -- /usr/local/bsystem/m2/maven-2.0.6 for you.)  
Plexus is a maven component, so it is possible that the maven install  
itself is corrupt.  Can you run the build from the command line (as  
the user hudson is running as)?

Rhett


On Apr 17, 2007, at 1:20 PM, Replogle, Andrew wrote:

> Hello Hudson Users,
>
>
>
> I picked up Hudson 1.102 to get the support for maven 2.0.6 and  
> we’re running on RHES 3.x and no matter what I try and build I get  
> the following error in the console:
>
>
>
> started[trunk] $ /usr/local/jdk1.5.0_05/jre/bin/java -cp /usr/local/
> apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-
> agent-1.102.jar:/usr/local/bsystem/m2/maven-2.0.6/core/boot/
> classworlds-1.1.jar hudson.maven.agent.Main /usr/local/bsystem/m2/
> maven-2.0.6 /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/
> lib/remoting-1.102.jar /usr/local/apache-tomcat-5.5.15/webapps/
> hudson/WEB-INF/lib/maven-interceptor-1.102.jarchannel startedFATAL:  
> nullhudson.util.IOException2        at hudson.maven.MavenBuild
> $Builder.call(MavenBuild.java:177)        at hudson.maven.MavenBuild
> $Builder.call(MavenBuild.java:136)        at  
> hudson.remoting.UserRequest.perform(UserRequest.java:57)        at  
> hudson.remoting.UserRequest.perform(UserRequest.java:22)        at  
> hudson.remoting.Request$2.run(Request.java:178)        at  
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)        at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)        at java.lang.Thread.run
> (Thread.java:595)Caused by:  
> java.lang.reflect.InvocationTargetException        at  
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)        at  
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)        at  
> java.lang.reflect.Method.invoke(Method.java:585)        at  
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:
> 315)        at org.codehaus.classworlds.Launcher.launch
> (Launcher.java:255)        at hudson.maven.agent.Main.launch
> (Main.java:70)        at hudson.maven.MavenBuild$Builder.call
> (MavenBuild.java:160)        ... 7 moreCaused by:  
> java.lang.IllegalStateException: The internal default plexus-
> bootstrap.xml is missing. This is highly irregular, your plexus JAR  
> is most likely corrupt.        at  
> org.codehaus.plexus.DefaultPlexusContainer.initializeConfiguration
> (DefaultPlexusContainer.java:1062)        at  
> org.codehaus.plexus.DefaultPlexusContainer.initialize
> (DefaultPlexusContainer.java:636)        at  
> org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)        
> at org.codehaus.plexus.embed.Embedder.start(Embedder.java:
> 183)        at org.apache.maven.cli.MavenCli.main(MavenCli.java:
> 156)        ... 15 more
>
>
> I’ve checked the md5sum of the war several times after downloading  
> it to make sure the war wasn’t corrupt  
> (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don’t  
> think this is a corruption issue.
>
>
>
> Is this possibly related to the maven 2.0.6 support or is this a  
> separate issue? Any assistance or direction is greatly appreciated.  
> Thanks =]
>
>
>
> Andrew
>
>

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

Reply | Threaded
Open this post in threaded view
|

RE: Re: issue with hudson 1.102

Replogle, Andrew
Rhett,

Thanks for the reply =]

We are currently executing several builds on the build server manually
as the same user as Hudson is executing the builds as without issue.

I also originally thought this might be our maven install specific or
perhaps an environment variable issue like LANG, but after finding out
our developers were building fine this way, I put that notion aside.

Andrew

-----Original Message-----
From: Rhett Sutphin [mailto:[hidden email]]
Sent: Tuesday, April 17, 2007 1:29 PM
To: [hidden email]
Subject: Re: issue with hudson 1.102

Hi,

> I've checked the md5sum of the war several times after downloading  
> it to make sure the war wasn't corrupt  
> (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don't  
> think this is a corruption issue.
>
>
> Is this possibly related to the maven 2.0.6 support or is this a  
> separate issue? Any assistance or direction is greatly appreciated.  
> Thanks =]
I'm not 100% sure of this, but I think Hudson uses your locally-
installed maven, even with the native m2 support.  (You can see it in  
the command string -- /usr/local/bsystem/m2/maven-2.0.6 for you.)  
Plexus is a maven component, so it is possible that the maven install  
itself is corrupt.  Can you run the build from the command line (as  
the user hudson is running as)?

Rhett


On Apr 17, 2007, at 1:20 PM, Replogle, Andrew wrote:

> Hello Hudson Users,
>
>
>
> I picked up Hudson 1.102 to get the support for maven 2.0.6 and  
> we're running on RHES 3.x and no matter what I try and build I get  
> the following error in the console:
>
>
>
> started[trunk] $ /usr/local/jdk1.5.0_05/jre/bin/java -cp /usr/local/
> apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-
> agent-1.102.jar:/usr/local/bsystem/m2/maven-2.0.6/core/boot/
> classworlds-1.1.jar hudson.maven.agent.Main /usr/local/bsystem/m2/
> maven-2.0.6 /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/
> lib/remoting-1.102.jar /usr/local/apache-tomcat-5.5.15/webapps/
> hudson/WEB-INF/lib/maven-interceptor-1.102.jarchannel startedFATAL:  
> nullhudson.util.IOException2        at hudson.maven.MavenBuild
> $Builder.call(MavenBuild.java:177)        at hudson.maven.MavenBuild
> $Builder.call(MavenBuild.java:136)        at  
> hudson.remoting.UserRequest.perform(UserRequest.java:57)        at  
> hudson.remoting.UserRequest.perform(UserRequest.java:22)        at  
> hudson.remoting.Request$2.run(Request.java:178)        at  
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)        at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)        at java.lang.Thread.run
> (Thread.java:595)Caused by:  
> java.lang.reflect.InvocationTargetException        at  
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)        at  
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)        at  
> java.lang.reflect.Method.invoke(Method.java:585)        at  
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:
> 315)        at org.codehaus.classworlds.Launcher.launch
> (Launcher.java:255)        at hudson.maven.agent.Main.launch
> (Main.java:70)        at hudson.maven.MavenBuild$Builder.call
> (MavenBuild.java:160)        ... 7 moreCaused by:  
> java.lang.IllegalStateException: The internal default plexus-
> bootstrap.xml is missing. This is highly irregular, your plexus JAR  
> is most likely corrupt.        at  
> org.codehaus.plexus.DefaultPlexusContainer.initializeConfiguration
> (DefaultPlexusContainer.java:1062)        at  
> org.codehaus.plexus.DefaultPlexusContainer.initialize
> (DefaultPlexusContainer.java:636)        at  
> org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)        
> at org.codehaus.plexus.embed.Embedder.start(Embedder.java:
> 183)        at org.apache.maven.cli.MavenCli.main(MavenCli.java:
> 156)        ... 15 more
>
>
> I've checked the md5sum of the war several times after downloading  
> it to make sure the war wasn't corrupt  
> (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don't  
> think this is a corruption issue.
>
>
>
> Is this possibly related to the maven 2.0.6 support or is this a  
> separate issue? Any assistance or direction is greatly appreciated.  
> Thanks =]
>
>
>
> Andrew
>
>

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

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

Reply | Threaded
Open this post in threaded view
|

Re: issue with hudson 1.102

Kohsuke Kawaguchi
Administrator
In reply to this post by Replogle, Andrew

Can you file this as an issue, as you say, I suspect a problem in Hudson.

Does this work with 2.0.4 or 2.0.5?

Replogle, Andrew wrote:

> Hello Hudson Users,
>
>  
>
> I picked up Hudson 1.102 to get the support for maven 2.0.6 and we're
> running on RHES 3.x and no matter what I try and build I get the
> following error in the console:
>
>  
>
> started
> [trunk] $ /usr/local/jdk1.5.0_05/jre/bin/java -cp
> /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-agent-1
> .102.jar:/usr/local/bsystem/m2/maven-2.0.6/core/boot/classworlds-1.1.jar
> hudson.maven.agent.Main /usr/local/bsystem/m2/maven-2.0.6
> /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/remoting-1.10
> 2.jar
> /usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-interce
> ptor-1.102.jar
> channel started
> FATAL: null
> hudson.util.IOException2
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:177)
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:136)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:57)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:22)
>         at hudson.remoting.Request$2.run(Request.java:178)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecuto
> r.java:650)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:675)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at hudson.maven.agent.Main.launch(Main.java:70)
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:160)
>         ... 7 more
> Caused by: java.lang.IllegalStateException: The internal default
> plexus-bootstrap.xml is missing. This is highly irregular, your plexus
> JAR is most likely corrupt.
>         at
> org.codehaus.plexus.DefaultPlexusContainer.initializeConfiguration(Defau
> ltPlexusContainer.java:1062)
>         at
> org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta
> iner.java:636)
>         at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
>         at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:156)
>         ... 15 more
>
>  
>
> I've checked the md5sum of the war several times after downloading it to
> make sure the war wasn't corrupt (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don't think
> this is a corruption issue.
>
>  
>
> Is this possibly related to the maven 2.0.6 support or is this a
> separate issue? Any assistance or direction is greatly appreciated.
> Thanks =]
>
>  
>
> Andrew
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

RE: Re: issue with hudson 1.102

Replogle, Andrew
I just tried with 2.0.5 and its working fine. I'll submit an issue.

Thanks =]

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Tuesday, April 17, 2007 7:45 PM
To: [hidden email]
Subject: Re: issue with hudson 1.102


Can you file this as an issue, as you say, I suspect a problem in
Hudson.

Does this work with 2.0.4 or 2.0.5?

Replogle, Andrew wrote:

> Hello Hudson Users,
>
>  
>
> I picked up Hudson 1.102 to get the support for maven 2.0.6 and we're
> running on RHES 3.x and no matter what I try and build I get the
> following error in the console:
>
>  
>
> started
> [trunk] $ /usr/local/jdk1.5.0_05/jre/bin/java -cp
>
/usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-agent-1
>
.102.jar:/usr/local/bsystem/m2/maven-2.0.6/core/boot/classworlds-1.1.jar
> hudson.maven.agent.Main /usr/local/bsystem/m2/maven-2.0.6
>
/usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/remoting-1.10
> 2.jar
>
/usr/local/apache-tomcat-5.5.15/webapps/hudson/WEB-INF/lib/maven-interce

> ptor-1.102.jar
> channel started
> FATAL: null
> hudson.util.IOException2
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:177)
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:136)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:57)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:22)
>         at hudson.remoting.Request$2.run(Request.java:178)
>         at
>
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecuto
> r.java:650)
>         at
>
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:675)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>         at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

> Impl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at hudson.maven.agent.Main.launch(Main.java:70)
>         at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:160)
>         ... 7 more
> Caused by: java.lang.IllegalStateException: The internal default
> plexus-bootstrap.xml is missing. This is highly irregular, your plexus
> JAR is most likely corrupt.
>         at
>
org.codehaus.plexus.DefaultPlexusContainer.initializeConfiguration(Defau
> ltPlexusContainer.java:1062)
>         at
>
org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta
> iner.java:636)
>         at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
>         at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:156)
>         ... 15 more
>
>  
>
> I've checked the md5sum of the war several times after downloading it
to
> make sure the war wasn't corrupt (a9f15d85c815c00d001029bcd6b8838d)
>
> Unless Tomcat is corrupting a jar in the explosion process I don't
think

> this is a corruption issue.
>
>  
>
> Is this possibly related to the maven 2.0.6 support or is this a
> separate issue? Any assistance or direction is greatly appreciated.
> Thanks =]
>
>  
>
> Andrew
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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