Re: core-integration-testing-maven-3 jobs hangs
Dennis Lundberg wrote: ExecuteJava daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on condition [0x0a63e000..0x0a63fa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:716) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:872) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1179) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:199) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528) Unless the decision gets made to require Java 1.6 for Maven 3.1+, I suggest to revert 1a1fe6d50802713d969ed08d6fa06dec53cf90e9, thereby allowing the thread pool to actually process its work queue. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
I now have a real windows pc to test that on - so I'll give it a spin before reverting/fixing. Kristian 2013/2/12 Benjamin Bentmann benjamin.bentm...@udo.edu Dennis Lundberg wrote: ExecuteJava daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on condition [0x0a63e000..**0x0a63fa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.**LockSupport.park(LockSupport.** java:118) at java.util.concurrent.locks.**AbstractQueuedSynchronizer.** parkAndCheckInterrupt(**AbstractQueuedSynchronizer.**java:716) at java.util.concurrent.locks.**AbstractQueuedSynchronizer.** doAcquireSharedInterruptibly(**AbstractQueuedSynchronizer.**java:872) at java.util.concurrent.locks.**AbstractQueuedSynchronizer.** acquireSharedInterruptibly(**AbstractQueuedSynchronizer.**java:1179) at java.util.concurrent.**CountDownLatch.await(**CountDownLatch.java:199) at org.apache.maven.artifact.**resolver.**DefaultArtifactResolver.**resolve( **DefaultArtifactResolver.java:**528) Unless the decision gets made to require Java 1.6 for Maven 3.1+, I suggest to revert 1a1fe6d50802713d969ed08d6fa06d**ec53cf90e9, thereby allowing the thread pool to actually process its work queue. Benjamin --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
Here's another attempt. It would seem that someone somewhere simply does not want people to do this! Here's a rundown on the hoops I've had to jump through so far... * jstack.exe is not available in Sun's Windows 1.5 JDK * jstack.exe from JDK 1.6 is not allowed to hook into a 1.5 JVM * SendSignal.exe which does 'kill -3 pid' gets Access denied * Finally I've resorted to turn of forking in the Ant build.xml by adding maven-compile.fork=false to the command line. Here's a thread dump that at least has some references to classes within org.apache.maven. This one looks like a hot candidate to me: org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528) Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_22-b03 mixed mode): WATCHDOG daemon prio=6 tid=0x06a92230 nid=0x1154 in Object.wait() [0x0a93f000..0x0a93f990] at java.lang.Object.wait(Native Method) - waiting on 0x4ebf44a0 (a org.apache.tools.ant.util.Watchdog) at org.apache.tools.ant.util.Watchdog.run(Watchdog.java:117) - locked 0x4ebf44a0 (a org.apache.tools.ant.util.Watchdog) at java.lang.Thread.run(Thread.java:595) ExecuteJava daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on condition [0x0a63e000..0x0a63fa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:716) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:872) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1179) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:199) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:349) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:343) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:318) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:287) at org.apache.maven.shared.artifact.resolver.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:140) at org.apache.maven.shared.artifact.resolver.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:187) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.resolveProjectArtifacts(ProcessRemoteResourcesMojo.java:714) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:620) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:997) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:511) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:146) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:545) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at org.apache.maven.cli.MavenCli.main(MavenCli.java:149) 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:592) at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) at
Re: core-integration-testing-maven-3 jobs hangs
An extremely simple solution would be to require JDK 1.6 to build Maven (but keep Java 5 runtime requirement)... /Anders On Thu, Jan 3, 2013 at 7:46 PM, Dennis Lundberg denn...@apache.org wrote: Here's another attempt. It would seem that someone somewhere simply does not want people to do this! Here's a rundown on the hoops I've had to jump through so far... * jstack.exe is not available in Sun's Windows 1.5 JDK * jstack.exe from JDK 1.6 is not allowed to hook into a 1.5 JVM * SendSignal.exe which does 'kill -3 pid' gets Access denied * Finally I've resorted to turn of forking in the Ant build.xml by adding maven-compile.fork=false to the command line. Here's a thread dump that at least has some references to classes within org.apache.maven. This one looks like a hot candidate to me: org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528) Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_22-b03 mixed mode): WATCHDOG daemon prio=6 tid=0x06a92230 nid=0x1154 in Object.wait() [0x0a93f000..0x0a93f990] at java.lang.Object.wait(Native Method) - waiting on 0x4ebf44a0 (a org.apache.tools.ant.util.Watchdog) at org.apache.tools.ant.util.Watchdog.run(Watchdog.java:117) - locked 0x4ebf44a0 (a org.apache.tools.ant.util.Watchdog) at java.lang.Thread.run(Thread.java:595) ExecuteJava daemon prio=6 tid=0x06a92790 nid=0x1078 waiting on condition [0x0a63e000..0x0a63fa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:716) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:872) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1179) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:199) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveWithExceptions(DefaultArtifactResolver.java:349) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:343) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:318) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:287) at org.apache.maven.shared.artifact.resolver.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:140) at org.apache.maven.shared.artifact.resolver.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:187) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.resolveProjectArtifacts(ProcessRemoteResourcesMojo.java:714) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:620) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:997) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:511) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:146) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:545) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at org.apache.maven.cli.MavenCli.main(MavenCli.java:149) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Re: core-integration-testing-maven-3 jobs hangs
Dennis, can you get a thread dump from your windows box? /Anders On Wed, Jan 2, 2013 at 5:07 AM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: A thread dump is worth a thousand words ;) K Den 2. jan. 2013 kl. 04:28 skrev Dennis Lundberg denn...@apache.org: Hi I've done some more digging into this and have come to the following conclusions: 1. It is not the ITs that are the problem - it's the building of core itself. 2. The build hangs when using Java 1.5, but succeeds using Java 1.6. 3. I have only verified this on Windows yet. Forensic report In build.xml I changed the value of the maven.debug property to -X to see what is happening. The timeout value of the java task inside the maven-compile target was increased to make sure it was large enough. Note that it is this timeout that is hit on Jenkins when the builds are aborted. When building with Java 1.5 the build halts between running maven-remote-resources-plugin:process and animal-sniffer-maven-plugin:1.6:check. In the following log output I have tried upgrading maven-remote-resources-plugin to the latest version, but that didn't make any difference. I used this command: ant.bat -file build.xml -DskipTests=true -Dmaven.home=G:\ws\m3-its/apache-maven-3-SNAPSHOT -Dmaven.home.exists.continue=true -Dmaven.repo.local=G:\ws\m3-its/.repository all With Java 1.5 ... [java] 19:55:50.379 [main] DEBUG o.a.m.p.i.DefaultMavenPluginManager - Configuring mojo org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-remote-resources-plugin:1.4, parent: sun.misc.Launcher$AppClassLoader@4a92e78c] [java] 19:55:50.389 [main] DEBUG Sisu - Initialize: org.codehaus.plexus.velocity.DefaultVelocityComponent@7aba175f [java] 19:55:50.419 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: site.resource.loader.class = 'org.codehaus.plexus.velocity.SiteResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: velocimacro.messages.on = 'false'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.loader = 'classpath,site'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: runtime.log.invalid.references = 'false'. [java] 19:55:50.549 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.manager.logwhenfound = 'false'. [java] 19:55:50.559 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Initializing Velocity, Calling init()... [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - *** [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Starting Apache Velocity v1.7 (compiled: 2010-11-19 12:14:37) [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - RuntimeInstance initializing. [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - LogSystem has been deprecated. Please use a LogChute implementation. [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initialization complete. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Stop [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Define [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Break [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive:
Re: core-integration-testing-maven-3 jobs hangs
So, my first ever thread dump. Hope it's the right stuff... Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_22-b03 mixed mode): WATCHDOG daemon prio=6 tid=0x072f1fe0 nid=0x1234 in Object.wait() [0x0b8df000..0x0b8dfa90] at java.lang.Object.wait(Native Method) - waiting on 0x477137a8 (a org.apache.tools.ant.util.Watchdog) at org.apache.tools.ant.util.Watchdog.run(Watchdog.java:117) - locked 0x477137a8 (a org.apache.tools.ant.util.Watchdog) at java.lang.Thread.run(Thread.java:595) Thread-78 daemon prio=6 tid=0x072f1d30 nid=0xcd0 in Object.wait() [0x0b7df000..0x0b7dfb10] at java.lang.Object.wait(Native Method) - waiting on 0x4772a938 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772a938 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) Thread-80 daemon prio=6 tid=0x072f1a80 nid=0x18f4 in Object.wait() [0x0b6df000..0x0b6df790] at java.lang.Object.wait(Native Method) - waiting on 0x4772afb8 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772afb8 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) Thread-79 daemon prio=6 tid=0x072f17d0 nid=0x112c in Object.wait() [0x0b3df000..0x0b3df810] at java.lang.Object.wait(Native Method) - waiting on 0x4772ac78 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772ac78 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) pool-1-thread-5 prio=6 tid=0x072f3f70 nid=0x17d0 waiting on condition [0x0b1df000..0x0b1df910] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-4 prio=6 tid=0x06c003e0 nid=0x1b1c waiting on condition [0x0b0df000..0x0b0df890] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-3 prio=6 tid=0x06b5c940 nid=0x1b14 waiting on condition [0x0afdf000..0x0afdf990] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-2 prio=6 tid=0x064f7e00 nid=0x1b80 waiting on condition [0x0aedf000..0x0aedfa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-1
Re: core-integration-testing-maven-3 jobs hangs
That process seems to be just waiting for some other process to complete. Use something like jps -lv to determine if there's more java processes around,determine if any of them seem to be relevant and thread dump them ;) Kristian 2013/1/2 Dennis Lundberg denn...@apache.org: So, my first ever thread dump. Hope it's the right stuff... Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.5.0_22-b03 mixed mode): WATCHDOG daemon prio=6 tid=0x072f1fe0 nid=0x1234 in Object.wait() [0x0b8df000..0x0b8dfa90] at java.lang.Object.wait(Native Method) - waiting on 0x477137a8 (a org.apache.tools.ant.util.Watchdog) at org.apache.tools.ant.util.Watchdog.run(Watchdog.java:117) - locked 0x477137a8 (a org.apache.tools.ant.util.Watchdog) at java.lang.Thread.run(Thread.java:595) Thread-78 daemon prio=6 tid=0x072f1d30 nid=0xcd0 in Object.wait() [0x0b7df000..0x0b7dfb10] at java.lang.Object.wait(Native Method) - waiting on 0x4772a938 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772a938 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) Thread-80 daemon prio=6 tid=0x072f1a80 nid=0x18f4 in Object.wait() [0x0b6df000..0x0b6df790] at java.lang.Object.wait(Native Method) - waiting on 0x4772afb8 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772afb8 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) Thread-79 daemon prio=6 tid=0x072f17d0 nid=0x112c in Object.wait() [0x0b3df000..0x0b3df810] at java.lang.Object.wait(Native Method) - waiting on 0x4772ac78 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.waitForInput(StreamPumper.java:229) - locked 0x4772ac78 (a org.apache.tools.ant.taskdefs.StreamPumper) at org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:126) at java.lang.Thread.run(Thread.java:595) pool-1-thread-5 prio=6 tid=0x072f3f70 nid=0x17d0 waiting on condition [0x0b1df000..0x0b1df910] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-4 prio=6 tid=0x06c003e0 nid=0x1b1c waiting on condition [0x0b0df000..0x0b0df890] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-3 prio=6 tid=0x06b5c940 nid=0x1b14 waiting on condition [0x0afdf000..0x0afdf990] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) pool-1-thread-2 prio=6 tid=0x064f7e00 nid=0x1b80 waiting on condition [0x0aedf000..0x0aedfa10] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) at
Re: core-integration-testing-maven-3 jobs hangs
Hi I've done some more digging into this and have come to the following conclusions: 1. It is not the ITs that are the problem - it's the building of core itself. 2. The build hangs when using Java 1.5, but succeeds using Java 1.6. 3. I have only verified this on Windows yet. Forensic report In build.xml I changed the value of the maven.debug property to -X to see what is happening. The timeout value of the java task inside the maven-compile target was increased to make sure it was large enough. Note that it is this timeout that is hit on Jenkins when the builds are aborted. When building with Java 1.5 the build halts between running maven-remote-resources-plugin:process and animal-sniffer-maven-plugin:1.6:check. In the following log output I have tried upgrading maven-remote-resources-plugin to the latest version, but that didn't make any difference. I used this command: ant.bat -file build.xml -DskipTests=true -Dmaven.home=G:\ws\m3-its/apache-maven-3-SNAPSHOT -Dmaven.home.exists.continue=true -Dmaven.repo.local=G:\ws\m3-its/.repository all With Java 1.5 ... [java] 19:55:50.379 [main] DEBUG o.a.m.p.i.DefaultMavenPluginManager - Configuring mojo org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-remote-resources-plugin:1.4, parent: sun.misc.Launcher$AppClassLoader@4a92e78c] [java] 19:55:50.389 [main] DEBUG Sisu - Initialize: org.codehaus.plexus.velocity.DefaultVelocityComponent@7aba175f [java] 19:55:50.419 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: site.resource.loader.class = 'org.codehaus.plexus.velocity.SiteResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: velocimacro.messages.on = 'false'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.loader = 'classpath,site'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: runtime.log.invalid.references = 'false'. [java] 19:55:50.549 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.manager.logwhenfound = 'false'. [java] 19:55:50.559 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Initializing Velocity, Calling init()... [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - *** [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Starting Apache Velocity v1.7 (compiled: 2010-11-19 12:14:37) [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - RuntimeInstance initializing. [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - LogSystem has been deprecated. Please use a LogChute implementation. [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initialization complete. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Stop [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Define [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Break [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate [java] 19:55:50.619 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Literal [java] 19:55:50.619 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Macro [java] 19:55:50.629 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive:
Re: core-integration-testing-maven-3 jobs hangs
A thread dump is worth a thousand words ;) K Den 2. jan. 2013 kl. 04:28 skrev Dennis Lundberg denn...@apache.org: Hi I've done some more digging into this and have come to the following conclusions: 1. It is not the ITs that are the problem - it's the building of core itself. 2. The build hangs when using Java 1.5, but succeeds using Java 1.6. 3. I have only verified this on Windows yet. Forensic report In build.xml I changed the value of the maven.debug property to -X to see what is happening. The timeout value of the java task inside the maven-compile target was increased to make sure it was large enough. Note that it is this timeout that is hit on Jenkins when the builds are aborted. When building with Java 1.5 the build halts between running maven-remote-resources-plugin:process and animal-sniffer-maven-plugin:1.6:check. In the following log output I have tried upgrading maven-remote-resources-plugin to the latest version, but that didn't make any difference. I used this command: ant.bat -file build.xml -DskipTests=true -Dmaven.home=G:\ws\m3-its/apache-maven-3-SNAPSHOT -Dmaven.home.exists.continue=true -Dmaven.repo.local=G:\ws\m3-its/.repository all With Java 1.5 ... [java] 19:55:50.379 [main] DEBUG o.a.m.p.i.DefaultMavenPluginManager - Configuring mojo org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-remote-resources-plugin:1.4, parent: sun.misc.Launcher$AppClassLoader@4a92e78c] [java] 19:55:50.389 [main] DEBUG Sisu - Initialize: org.codehaus.plexus.velocity.DefaultVelocityComponent@7aba175f [java] 19:55:50.419 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: site.resource.loader.class = 'org.codehaus.plexus.velocity.SiteResourceLoader'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: velocimacro.messages.on = 'false'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.loader = 'classpath,site'. [java] 19:55:50.539 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: runtime.log.invalid.references = 'false'. [java] 19:55:50.549 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Setting property: resource.manager.logwhenfound = 'false'. [java] 19:55:50.559 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Initializing Velocity, Calling init()... [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - *** [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Starting Apache Velocity v1.7 (compiled: 2010-11-19 12:14:37) [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - RuntimeInstance initializing. [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [java] 19:55:50.569 [main] DEBUG o.c.p.v.DefaultVelocityComponent - LogSystem has been deprecated. Please use a LogChute implementation. [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [java] 19:55:50.579 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Default ResourceManager initialization complete. [java] 19:55:50.599 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Stop [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Define [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Break [java] 19:55:50.609 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate [java] 19:55:50.619 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System Directive: org.apache.velocity.runtime.directive.Literal [java] 19:55:50.619 [main] DEBUG o.c.p.v.DefaultVelocityComponent - Loaded System
Re: core-integration-testing-maven-3 jobs hangs
On 2012-12-14 00:29, Brett Porter wrote: On 13/12/2012, at 9:15 PM, Anders Hammar and...@hammar.net wrote: Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. Git is now found on the windows nodes, so I guess your mail triggered some action. But we also have the same problem on the solaris nodes. I'll join the builds list and ask about that. I installed it, but understood that Dennis still need to change something in the build before it would work: http://mail-archives.apache.org/mod_mbox/www-builds/201212.mbox/%3C50BFBBA6.5010809%40apache.org%3E I've tried tweaking the Jenkins job on the Windows slave, but without success. The build fails with this error: --- BUILD FAILED f:\ws\m3-its\maven-3-trunk\build.xml:253: Timeout: killed the sub-process Total time: 10 minutes 58 seconds Build step 'Invoke Ant' marked build as failure --- The thing is that I've disabled all the timeouts I can find... Does anyone have more ideas? Here's a link to the latest build: https://builds.apache.org/job/core-it-maven-3-win/294/console I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
The pattern I see is that all jobs that build with JDK 1.5 hangs. This includes the windows node. /Anders On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg denn...@apache.org wrote: On 2012-12-14 00:29, Brett Porter wrote: On 13/12/2012, at 9:15 PM, Anders Hammar and...@hammar.net wrote: Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. Git is now found on the windows nodes, so I guess your mail triggered some action. But we also have the same problem on the solaris nodes. I'll join the builds list and ask about that. I installed it, but understood that Dennis still need to change something in the build before it would work: http://mail-archives.apache.org/mod_mbox/www-builds/201212.mbox/%3C50BFBBA6.5010809%40apache.org%3E I've tried tweaking the Jenkins job on the Windows slave, but without success. The build fails with this error: --- BUILD FAILED f:\ws\m3-its\maven-3-trunk\build.xml:253: Timeout: killed the sub-process Total time: 10 minutes 58 seconds Build step 'Invoke Ant' marked build as failure --- The thing is that I've disabled all the timeouts I can find... Does anyone have more ideas? Here's a link to the latest build: https://builds.apache.org/job/core-it-maven-3-win/294/console I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
Igor and I have successfully run the ITs on 1.5. Igor did it on Linux and I did it on OS X. So I think it's some interaction on the CI server. I can't get it to work on Jenkins or Hudson, even with a lot of memory. On Dec 16, 2012, at 2:43 PM, Anders Hammar and...@hammar.net wrote: The pattern I see is that all jobs that build with JDK 1.5 hangs. This includes the windows node. /Anders On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg denn...@apache.org wrote: On 2012-12-14 00:29, Brett Porter wrote: On 13/12/2012, at 9:15 PM, Anders Hammar and...@hammar.net wrote: Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. Git is now found on the windows nodes, so I guess your mail triggered some action. But we also have the same problem on the solaris nodes. I'll join the builds list and ask about that. I installed it, but understood that Dennis still need to change something in the build before it would work: http://mail-archives.apache.org/mod_mbox/www-builds/201212.mbox/%3C50BFBBA6.5010809%40apache.org%3E I've tried tweaking the Jenkins job on the Windows slave, but without success. The build fails with this error: --- BUILD FAILED f:\ws\m3-its\maven-3-trunk\build.xml:253: Timeout: killed the sub-process Total time: 10 minutes 58 seconds Build step 'Invoke Ant' marked build as failure --- The thing is that I've disabled all the timeouts I can find... Does anyone have more ideas? Here's a link to the latest build: https://builds.apache.org/job/core-it-maven-3-win/294/console I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
Re: core-integration-testing-maven-3 jobs hangs
2012/12/14 Anders Hammar and...@hammar.net: I tried tweaking through: -Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m but it didn't make any difference. I did more tests without more success. I need to have a look on the nodes as it's a bit weird. I don't have much in-depth knowledge about the darker secrets of Java memory management so it was just a test. Anyone with a greater brain is welcome to suggest something to try. Or, we could just accept that JDK 1.6+ is required to build core (but still support Java 5 as target). /Anders On Fri, Dec 14, 2012 at 8:06 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I have also seen the core it's hang in a quite nasty manner if permgen is running lowish. Kristian 2012/12/14 Anders Hammar and...@hammar.net: I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7 builds works just fine it seems. The turnaround for trying things on CI is so long though I haven't had the patience to test bumping the JDK on one of the problematic jobs (yet). /Anders - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
/me wants thread dump to put in drink :) K Den 16. des. 2012 kl. 04:57 skrev Olivier Lamy ol...@apache.org: 2012/12/14 Anders Hammar and...@hammar.net: I tried tweaking through: -Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m but it didn't make any difference. I did more tests without more success. I need to have a look on the nodes as it's a bit weird. I don't have much in-depth knowledge about the darker secrets of Java memory management so it was just a test. Anyone with a greater brain is welcome to suggest something to try. Or, we could just accept that JDK 1.6+ is required to build core (but still support Java 5 as target). /Anders On Fri, Dec 14, 2012 at 8:06 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I have also seen the core it's hang in a quite nasty manner if permgen is running lowish. Kristian 2012/12/14 Anders Hammar and...@hammar.net: I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7 builds works just fine it seems. The turnaround for trying things on CI is so long though I haven't had the patience to test bumping the JDK on one of the problematic jobs (yet). /Anders - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
I tried tweaking through: -Xmx512m -Xms512m -XX:MaxPermSize=256m -XX:PermSize=128m but it didn't make any difference. I don't have much in-depth knowledge about the darker secrets of Java memory management so it was just a test. Anyone with a greater brain is welcome to suggest something to try. Or, we could just accept that JDK 1.6+ is required to build core (but still support Java 5 as target). /Anders On Fri, Dec 14, 2012 at 8:06 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I have also seen the core it's hang in a quite nasty manner if permgen is running lowish. Kristian 2012/12/14 Anders Hammar and...@hammar.net: I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7 builds works just fine it seems. The turnaround for trying things on CI is so long though I haven't had the patience to test bumping the JDK on one of the problematic jobs (yet). /Anders - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. Git is now found on the windows nodes, so I guess your mail triggered some action. But we also have the same problem on the solaris nodes. I'll join the builds list and ask about that. /Anders /Anders On Sun, Dec 2, 2012 at 9:38 PM, Dennis Lundberg denn...@apache.org wrote: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
On 13/12/2012, at 9:15 PM, Anders Hammar and...@hammar.net wrote: Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. Git is now found on the windows nodes, so I guess your mail triggered some action. But we also have the same problem on the solaris nodes. I'll join the builds list and ask about that. I installed it, but understood that Dennis still need to change something in the build before it would work: http://mail-archives.apache.org/mod_mbox/www-builds/201212.mbox/%3C50BFBBA6.5010809%40apache.org%3E I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7 builds works just fine it seems. The turnaround for trying things on CI is so long though I haven't had the patience to test bumping the JDK on one of the problematic jobs (yet). /Anders - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
I have also seen the core it's hang in a quite nasty manner if permgen is running lowish. Kristian 2012/12/14 Anders Hammar and...@hammar.net: I see the hanging too... haven't looked into where it gets stuck any further though. Perhaps it's using an authenticated URL to checkout additional stuff as part of the bootstrap? One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7 builds works just fine it seems. The turnaround for trying things on CI is so long though I haven't had the patience to test bumping the JDK on one of the problematic jobs (yet). /Anders - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
core-integration-testing-maven-3 jobs hangs
The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders
Re: core-integration-testing-maven-3 jobs hangs
Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
Can we have a thread dump of that? K Den 2. des. 2012 kl. 21:39 skrev Dennis Lundberg denn...@apache.org: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
It's the core-integration-testing-maven-3 job that hangs. I've aborted it a few times hoping it would fix itself somehow. No luck though. Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? /Anders On Sun, Dec 2, 2012 at 9:38 PM, Dennis Lundberg denn...@apache.org wrote: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
On 2012-12-02 22:01, Anders Hammar wrote: It's the core-integration-testing-maven-3 job that hangs. I've aborted it a few times hoping it would fix itself somehow. No luck though. Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. /Anders On Sun, Dec 2, 2012 at 9:38 PM, Dennis Lundberg denn...@apache.org wrote: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
The Windows node is one, but I believe I saw the same problem on some other node as well. /Anders (mobile) Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org: On 2012-12-02 22:01, Anders Hammar wrote: It's the core-integration-testing-maven-3 job that hangs. I've aborted it a few times hoping it would fix itself somehow. No luck though. Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. /Anders On Sun, Dec 2, 2012 at 9:38 PM, Dennis Lundberg denn...@apache.org wrote: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
The Windows node is one, but I believe I saw the same problem on some other node as well. The same problem on the solaris node as well. /Anders /Anders (mobile) Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org: On 2012-12-02 22:01, Anders Hammar wrote: It's the core-integration-testing-maven-3 job that hangs. I've aborted it a few times hoping it would fix itself somehow. No luck though. Also, there's some problems with Jenkins not finding git installation on some nodes. But that's a different topic, but possibly related to the upgrade? If you mean the Windows node, I've already asked about that on builds@a.o but haven't gotten a reply yet. /Anders On Sun, Dec 2, 2012 at 9:38 PM, Dennis Lundberg denn...@apache.org wrote: Hi Anders It looks like ASF Jenkins has been upgraded to 1.492, which should help us with the unwanted constant rebuilds in some of our other projects. Which jobs are hung? I can only see one: core-integration-testing-maven-3-embedded On 2012-12-02 20:12, Anders Hammar wrote: The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. /Anders -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: core-integration-testing-maven-3 jobs hangs
The core-integration-testing-maven-3 jobs has started to hang since yesterday morning (whatever timezone the CI is showing). I have no clue how to figure out why. I've disabled the core-integration-testing-maven-3 job for now. We're just blocking other build jobs as it is now. As I pointed out, I have no idea how to solve this. Don't know if we can get a thread dump. /Anders /Anders
