[JBoss-dev] Re: FW: jboss-remoting-testsuite-1.5 Thread Dump

Tue, 24 Jan 2006 08:42:19 -0800

Have made the change and checked in. Should be IOException that is thrown, but can't hurt to check for all. 

Ryan Campbell wrote:

Tom,
Here is the stack trace from a hung remoting testsuite on jdk 1.5. It looks like all of the threads have exited, but the test is still trying to increment the count, and hasn’t found an exception. Perhaps the catch block should be expanded to include any throwable? Rajesh is testing to see if this allows the test to fail instead of hanging. 


ie,

               catch(Throwable e)

               {

                  error = true;

                  assertTrue("Error: " + e.getMessage(), false);

               }


------------------------------------------------------------------------

*From:* Rajesh Rajasekaran
*Sent:* Monday, January 23, 2006 4:54 PM
*To:* Ryan Campbell
*Subject:* RE: jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors 


Stack trace of thread dump


    [junit] Running org.jboss.test.remoting.util.PortUtilTestCase
[junit] Full thread dump Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode):
[junit] "Low Memory Detector" daemon prio=1 tid=0x8df3a4e0 nid=0x4ec5 runnable [0x00000000..0x00000000]
[junit] "CompilerThread1" daemon prio=1 tid=0x8df39140 nid=0x4ec4 waiting on condition [0x00000000..0x8da79788]
[junit] "CompilerThread0" daemon prio=1 tid=0x8df38200 nid=0x4ec3 waiting on condition [0x00000000..0x8dafa708]
[junit] "AdapterThread" daemon prio=1 tid=0x8df37280 nid=0x4ec2 waiting on condition [0x00000000..0x00000000]
[junit] "Signal Dispatcher" daemon prio=1 tid=0x8df36460 nid=0x4ec1 waiting on condition [0x00000000..0x00000000]
[junit] "Finalizer" daemon prio=1 tid=0x8df2cad0 nid=0x4ec0 in Object.wait() [0x8de7e000..0x8de7e770] 

    [junit]     at java.lang.Object.wait(Native Method)
[junit] - waiting on <0x925138d0> (a java.lang.ref.ReferenceQueue$Lock)
[junit] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116) 

    [junit]     - locked <0x925138d0> (a java.lang.ref.ReferenceQueue$Lock)
[junit] at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
[junit] at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
[junit] "Reference Handler" daemon prio=1 tid=0x8df2be90 nid=0x4ebf in Object.wait() [0x8deff000..0x8deff6f0] 

    [junit]     at java.lang.Object.wait(Native Method)

    [junit]     - waiting on <0x9254a538> (a java.lang.ref.Reference$Lock)

    [junit]     at java.lang.Object.wait(Object.java:474)
[junit] at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) 

    [junit]     - locked <0x9254a538> (a java.lang.ref.Reference$Lock)
[junit] "main" prio=1 tid=0x0805d188 nid=0x4eb7 waiting on condition [0xbfffb000..0xbfffc118] 

    [junit]     at java.lang.Thread.sleep(Native Method)
[junit] at org.jboss.test.remoting.util.PortUtilTestCase.testFindingFreePorts(PortUtilTestCase.java:83)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 

    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)

    [junit]     at junit.framework.TestCase.runTest(TestCase.java:154)

    [junit]     at junit.framework.TestCase.runBare(TestCase.java:127)

    [junit]     at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124) 

    [junit]     at junit.framework.TestResult.run(TestResult.java:109)

    [junit]     at junit.framework.TestCase.run(TestCase.java:118)

    [junit]     at junit.framework.TestSuite.runTest(TestSuite.java:208)

    [junit]     at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:289)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:656)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:558) 


    [junit] "VM Thread" prio=1 tid=0x8df29310 nid=0x4ebe runnable
[junit] "GC task thread#0 (ParallelGC)" prio=1 tid=0x080e3930 nid=0x4eba runnable
[junit] "GC task thread#1 (ParallelGC)" prio=1 tid=0x080e3d18 nid=0x4ebb runnable
[junit] "GC task thread#2 (ParallelGC)" prio=1 tid=0x080e4100 nid=0x4ebc runnable
[junit] "GC task thread#3 (ParallelGC)" prio=1 tid=0x080e48e0 nid=0x4ebd runnable
[junit] "VM Periodic Task Thread" prio=1 tid=0x8df3ba00 nid=0x4ec6 waiting on condition 


------------------------------------------------------------------------

*From:* Ryan Campbell
*Sent:* Monday, January 23, 2006 2:57 PM
*To:* Tom Elrod
*Cc:* QA
*Subject:* RE: jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
I guess this is an intermittent problem? 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to