Build Hang with AS7 Master...
by Jess Sightler
My build is consistently hanging at:
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.276 sec
Running org.jboss.as.server.test.ServerControllerUnitTestCase
The thread dump looks like this:
Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.12-b01 mixed mode):
"MSC service thread 1-4" prio=10 tid=0x00007ff98c002000 nid=0x6d88 waiting on condition [0x00007ff9ad7a6000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000d8f616c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"MSC service thread 1-3" prio=10 tid=0x00007ff988001800 nid=0x6d87 waiting on condition [0x00007ff9ad8a7000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000d8f616c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"MSC service thread 1-2" prio=10 tid=0x00007ff994001800 nid=0x6d86 waiting on condition [0x00007ff9ad9a8000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000d8f616c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"MSC service thread 1-1" prio=10 tid=0x00007ff9d44fd000 nid=0x6d85 waiting on condition [0x00007ff9adaa9000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000d8f616c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"Reference Reaper" daemon prio=10 tid=0x00007ff9d44db800 nid=0x6d84 in Object.wait() [0x00007ff9add3a000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000d901b830> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
- locked <0x00000000d901b830> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
at org.jboss.modules.ref.References$ReaperThread.run(References.java:68)
"Low Memory Detector" daemon prio=10 tid=0x00007ff9d40b8000 nid=0x6d82 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"C2 CompilerThread1" daemon prio=10 tid=0x00007ff9d40b5800 nid=0x6d81 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"C2 CompilerThread0" daemon prio=10 tid=0x00007ff9d40b3000 nid=0x6d80 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=10 tid=0x00007ff9d40b1000 nid=0x6d7f waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=10 tid=0x00007ff9d4094000 nid=0x6d7e in Object.wait() [0x00007ff9d045d000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000d80b1300> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
- locked <0x00000000d80b1300> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00007ff9d4092000 nid=0x6d7d in Object.wait() [0x00007ff9d055e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000d80b11d8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:485)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x00000000d80b11d8> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=0x00007ff9d4006800 nid=0x6d77 waiting on condition [0x00007ff9d8f68000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000d9143de0> (a java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207)
at org.jboss.as.server.test.ServerControllerUnitTestCase.beforeClass(ServerControllerUnitTestCase.java:106)
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:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
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:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
"VM Thread" prio=10 tid=0x00007ff9d408b800 nid=0x6d7c runnable
"GC task thread#0 (ParallelGC)" prio=10 tid=0x00007ff9d4019800 nid=0x6d78 runnable
"GC task thread#1 (ParallelGC)" prio=10 tid=0x00007ff9d401b800 nid=0x6d79 runnable
"GC task thread#2 (ParallelGC)" prio=10 tid=0x00007ff9d401d800 nid=0x6d7a runnable
"GC task thread#3 (ParallelGC)" prio=10 tid=0x00007ff9d401f000 nid=0x6d7b runnable
"VM Periodic Task Thread" prio=10 tid=0x00007ff9d40c2800 nid=0x6d83 waiting on condition
JNI global references: 1316
Heap
PSYoungGen total 35840K, used 26636K [0x00000000d80b0000, 0x00000000da8a0000, 0x0000000100000000)
eden space 30784K, 86% used [0x00000000d80b0000,0x00000000d9ab30f8,0x00000000d9ec0000)
from space 5056K, 0% used [0x00000000da3b0000,0x00000000da3b0000,0x00000000da8a0000)
to space 5056K, 0% used [0x00000000d9ec0000,0x00000000d9ec0000,0x00000000da3b0000)
PSOldGen total 81856K, used 0K [0x0000000088200000, 0x000000008d1f0000, 0x00000000d80b0000)
object space 81856K, 0% used [0x0000000088200000,0x0000000088200000,0x000000008d1f0000)
PSPermGen total 21248K, used 12820K [0x0000000083000000, 0x00000000844c0000, 0x0000000088200000)
object space 21248K, 60% used [0x0000000083000000,0x0000000083c852a0,0x00000000844c0000)
Any ideas?
Thanks,
--
Jess Sightler
Red Hat Consulting
Mobile:704-916-9383
http://www.redhat.com
10 years, 11 months
Using FindBugs effectively
by Stephen Coy
Hi there,
Some of you may have noticed that I've been raising seemingly random JIRAs related to incorrect code.
During regular project work I use FindBugs quite a bit, especially when I'm dropped into a job with an existing code base.
One of the ways of using FindBugs is by setting it up in Maven and getting it to run reports for you. I gather that this is what you guys have attempted in the past. The problem with this is that it generates reams of paper (so to speak), often containing more false positives than useful information.
As I'm an eclipse user, I've installed the FindBugs plugin. When you're working on a particular module it's pretty easy to run FindBugs across it and see what it has to say:
You can see that it's not exactly overwhelming and you can ignore the noise (there's a lot of it in some unit tests) and zero in on the suspect stuff quite easily. For example, there's many instances of NP_NULL_ON_SOME_PATH such as:
> Possible null pointer dereference of AbstractOperationContext.activeStep in org.jboss.as.controller.AbstractOperationContext.addStep(OperationStepHandler, OperationContext$Stage, boolean)
ie. a value is tested for null, but is dereferenced later anyway.
If you decide to try it, grab the version from <http://findbugs.sourceforge.net/downloads.html> because the version in the Eclipse Marketplace seems to be broken.
Cheers,
Steve Coy
(Hopefully the image makes it through the mailing list)
10 years, 11 months
as7-master-testsuite-ip6 - Build # 6070 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 6070 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/6070
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
FAILED: org.jboss.as.test.integration.osgi.stilts.StompletTestCase.org.jboss.as.test.integration.osgi.stilts.StompletTestCase
Error Message:
java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0 Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26 Caused by: java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.stilts-stomplet-server-bundle:0.1.26 Caused by: org.jboss.modules.ModuleNotFoundException: deployment.stilts-stomplet-server-bundle:0.1.26"}}
10 years, 11 months
as7-master-testsuite-ip6 - Build # 6058 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 6058 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/6058
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
FAILED: org.jboss.as.test.integration.osgi.stilts.StompletTestCase.org.jboss.as.test.integration.osgi.stilts.StompletTestCase
Error Message:
java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0 Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26 Caused by: java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.stilts-stomplet-server-bundle:0.1.26 Caused by: org.jboss.modules.ModuleNotFoundException: deployment.org.jboss.netty:3.4.5.Final"}}
10 years, 12 months
