gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: excalibur-compatibility deadlock problem
Date Mon, 31 Mar 2003 14:44:51 GMT
Leo Simons wrote:

 > http://lsd.student.utwente.nl/gump/excalibur-compatibility.html:
 >
 > [junit] Testcase: testDeadLock took 0.328 sec
 > [junit] FAILED
 > [junit] null
 > [junit] junit.framework.AssertionFailedError
 > [junit] at 
org.apache.avalon.excalibur.concurrent.test.ReadWriteLockTestCase.testDeadLock(ReadWriteLockTestCase.java:406)

[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] Testcase: testDeadLock BUILD FAILED
 >
 > file:///data/gump/avalon-excalibur/compatibility/build.xml:169: Test
 >
 > org.apache.avalon.excalibur.concurrent.test.ReadWriteLockTestCase 
failed Total time: 47 seconds
 >
 > ---
 >
 > this is on Red Hat 8.0 with Sun JDK 1.4.1. I'll argue that's an 
important platform to support!
 >
 > is this a known issue?


It's a race condition leading to a deadlock--it passes on my machine.
But that is why we are deprecating the use of all the stuff in
compatibility.  I don't want to spend time and energy trying to
bug fix code we aren't supporting.



Mime
View raw message