Bugs item #636227, was opened at 2002-11-10 16:05
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=636227&group_id=22866
Category: JBossTest
Group: CVS HEAD
Status: Open
Resolution: None
Priority: 5
Submitted By: Chris Kimpton (kimptoc)
Assigned to: Adrian Brock (ejort)
Summary: testsuite generally fails to complete
Initial Comment:
Hi,
I have run the full testsuite (testsuite/build.xml, target
test) several times but it rarely completes.
The machine is doing nothing else - 2 x 1.3GHZ cpu,
1GB ram - left run for 15 hours plus. Redhat 7.2, sun
jdk1.3.1_06
Tried using kill -SIGHUP, but it seemed to kill the JVM
rathing giving a thread dump.
Regards,
Chris
----------------------------------------------------------------------
>Comment By: Chris Kimpton (kimptoc)
Date: 2002-11-12 19:36
Message:
Logged In: YES
user_id=39204
Here is the thread dump from the testsuite
thread:
"WATCHDOG" daemon prio=1 tid=0x741f0e48
nid=0x75f8 waiting on monitor [0x7192a00
0..0x7192a870]
at
java.lang.Object.wait(Native Method)
at
org.apache.tools.ant.util.Watchdog.run(Watchdog.java:116)
at
java.lang.Thread.run(Thread.java:479)
"Thread-106" daemon
prio=1 tid=0x741f0ce0 nid=0x75f7 waiting on monitor
[0x7172a
000..0x7172a870]
at java.lang.Object.wait(Native
Method)
at
java.io.PipedInputStream.read(PipedInputStream.java:227)
at
java.lang.ProcessInputStream.read(UNIXProcess.java:345)
at
java.io.PipedInputStream.read(PipedInputStream.java:272)
at
java.io.InputStream.read(InputStream.java:86)
at
org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:105)
at java.lang.Thread.run(Thread.java:479)
"Thread-105"
daemon prio=1 tid=0x741f0b78 nid=0x75f6 waiting on monitor
[0x7152a
000..0x7152a870]
at java.lang.Object.wait(Native
Method)
at
java.io.PipedInputStream.read(PipedInputStream.java:227)
at
java.lang.ProcessInputStream.read(UNIXProcess.java:345)
at
java.io.PipedInputStream.read(PipedInputStream.java:272)
at
java.io.InputStream.read(InputStream.java:86)
at
org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:105)
at java.lang.Thread.run(Thread.java:479)
"stderr reader
pid=30195" daemon prio=1 tid=0x741f0a10 nid=0x75f5 runnable
[0x71
32a000..0x7132a870]
at
java.io.FileInputStream.readBytes(Native Method)
at
java.io.FileInputStream.read(FileInputStream.java:161)
at
java.lang.ProcessInputStream.run(UNIXProcess.java:385)
at
java.lang.Thread.run(Thread.java:479)
"stdout reader
pid=30195" daemon prio=1 tid=0x741f08d8 nid=0x75f4 runnable
[0x70
aff000..0x70aff870]
at
java.io.FileInputStream.readBytes(Native Method)
at
java.io.FileInputStream.read(FileInputStream.java:161)
at
java.lang.ProcessInputStream.run(UNIXProcess.java:385)
at
java.lang.Thread.run(Thread.java:479)
"process forker"
daemon prio=1 tid=0x6e9bcdf0 nid=0x6cea waiting on monitor
[0x6
f6ff000..0x6f6ff870]
at java.lang.Object.wait(Native
Method)
at java.lang.UNIXProcessForker.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"process reaper"
daemon prio=1 tid=0x6e9d6c88 nid=0x6ce9 runnable
[0x6f4ff000..0
x6f4ff870]
at
java.lang.UNIXProcessReaper.run(Native Method)
at
java.lang.Thread.run(Thread.java:479)
"Signal Dispatcher"
daemon prio=1 tid=0x808e178 nid=0x6ce7 waiting on monitor
[0
..0]
"Finalizer" daemon prio=1 tid=0x8086d98
nid=0x6ce4 waiting on monitor [0x6df6e00
0..0x6df6e870]
at
java.lang.Object.wait(Native Method)
at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference
Handler" daemon prio=1 tid=0x8085280 nid=0x6ce3 waiting on
monitor [0
x6dd6e000..0x6dd6e870]
at
java.lang.Object.wait(Native Method)
at
java.lang.Object.wait(Object.java:415)
at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
"main"
prio=1 tid=0x804e6f0 nid=0x6cc6 waiting on monitor
[0xbfffc000..0xbfffd2b
4]
at java.lang.Object.wait(Native
Method)
at java.lang.Object.wait(Object.java:415)
at
java.lang.UNIXProcess.waitFor(UNIXProcess.java:213)
at
org.apache.tools.ant.taskdefs.Execute.waitFor(Execute.java:467)
at
org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:449)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForke
d(JUnitTask.java:680)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitT
ask.java:554)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitT
ask.java:527)
at org.apache.tools.ant.Task.perform(Task.java:319)
at
org.apache.tools.ant.Target.execute(Target.java:309)
at
org.apache.tools.ant.Target.performTasks(Target.java:336)
at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at
org.apache.tools.ant.Main.start(Main.java:196)
at
org.apache.tools.ant.Main.main(Main.java:235)
"VM
Thread" prio=1 tid=0x80822f8 nid=0x6ce2 runnable
"VM
Periodic Task Thread" prio=1 tid=0x808cdc8 nid=0x6ce5 waiting on
monitor
"Suspend Checker Thread" prio=1 tid=0x808d7a0
nid=0x6ce6 runnable
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2002-11-12 15:33
Message:
Logged In: YES
user_id=9459
Hi Chris,
Do you see where ant forks the test? PID 24527
Try running
kill -s sigquit 24527
You might need to run the testsuite from the command
line. I don't know where the output will go if you are
running it from cron
It would be useful to get a threaddump of the
server as well.
Regards,
Adrian
----------------------------------------------------------------------
Comment By: Chris Kimpton (kimptoc)
Date: 2002-11-12 10:02
Message:
Logged In: YES
user_id=39204
Hi,
I have it running now (a fresh checkout, just running the unit
tests - been going about 1 hour - at 9:30AM GMT).
You can get the
pstree output
here:
http://jboss.kimptoc.net/pstree.txt
It seems to
have stopped somewhere different now...
Regards,
Chris
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2002-11-11 15:12
Message:
Logged In: YES
user_id=9459
I noticed a typo for "haltonfailure".
I'd be suprised if this was the cause, otherwise
other people would have seen the problem.
Regards,
Adrian
----------------------------------------------------------------------
Comment By: Chris Kimpton (kimptoc)
Date: 2002-11-11 14:04
Message:
Logged In: YES
user_id=39204
Hi,
Yes - it does seem a little random.
The full details are on this website:
http://jboss.kimptoc.net/jboss-all
[don't worry - it is jboss-head not all...]
I was running jboss direct from CVS - no modifications, extra
jars or config.
Test log is here:
http://jboss.kimptoc.net/jboss-all/build/cronjob_test.log
The specific report you mentioned is here:
http://jboss.kimptoc.net/jboss-
all/testsuite/output/reports/TEST-
org.jboss.test.naming.test.ExternalContextUnitTestCase.xml
I can run it again later and capture the pstree output.
Although I am pretty sure I see the ant java process in ps - as
I have to kill them all off manually when this happens...
Chris
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2002-11-11 12:09
Message:
Logged In: YES
user_id=9459
That's a bit random.
This test does nothing unless you have
external contexts configured.
What do you get in
output/reports/TEST-
org.jboss.test.naming.test.ExternalContextUnitTestCase.xml
I'm beginning to suspect a bug in ant/junit
especially since you are seeing a hang rather than timeout.
What output do you get from pstree, can you see
ant-java forking java?
Do you have any jars in jre/lib/ext?
Regards,
Adrian
----------------------------------------------------------------------
Comment By: Chris Kimpton (kimptoc)
Date: 2002-11-11 08:35
Message:
Logged In: YES
user_id=39204
2002-11-10 20:28:29,005 DEBUG
[org.jboss.test.naming.test.ExternalContextUnitTestCase]
JBossTestServices(),
className=org.jboss.test.naming.test.ExternalContextUnitTestCase
2002-
11-10 20:28:29,368 DEBUG
[org.jboss.test.naming.test.ExternalContextUnitTestCase]
JBossTestServices(),
className=org.jboss.test.naming.test.ExternalContextUnitTestCase
2002-
11-10 20:28:29,803 DEBUG
[org.jboss.test.naming.test.ExternalContextUnitTestCase] No
ExternalContext names exist
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2002-11-10 23:05
Message:
Logged In: YES
user_id=9459
Hi Chris,
Can you attach
testsuite/output/log/test.log
from the hanging test.
Regards,
Adrian
----------------------------------------------------------------------
Comment By: Chris Kimpton (kimptoc)
Date: 2002-11-10 22:31
Message:
Logged In: YES
user_id=39204
Hi,
I just tried running the tests-unit target on a freshly checked
out set of code and still it hangs...
I tried SIGQUIT - on several main java processes - but still did
not see any thread dump in the server.log - or does it go to
the console log?
Thanks,
Chris
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2002-11-10 17:05
Message:
Logged In: YES
user_id=175228
SIGQUIT is the correct signal to use to generate a thread
dump.
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2002-11-10 16:42
Message:
Logged In: YES
user_id=9459
Hi Chris,
Can you try it again?
I saw a deadlock with OIL yesterday, it was actually
a deadlock across two VMs during the connection close.
I saw it as a timeout rather than a permenant hang
though.
I also found a problem where the dead letter queue
wasn't being used because of incorrect xml parsing.
This led to infinite redelivery of messages to MDBs.
I've committed these fixes now.
Regards,
Adrian
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=636227&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by:
To learn the basics of securing your web site with SSL,
click here to get a FREE TRIAL of a Thawte Server Certificate:
http://www.gothawte.com/rd522.html
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
