Re: [PATCH] Re: Deadlock in ReaderWriterLock after calling LogManager.shutdown ()

2003-06-21 Thread Andy McBride
t;22:04:37 - > >@@ -485,6 +485,7 @@ > > } else { > > result = aai.getAllAppenders(); > > } > >+ lock.releaseReadLock(); > > return result; > >} > > > > > >On Thu, 19 Jun 2003 01:58:22 +010

[PATCH] Re: Deadlock in ReaderWriterLock after calling LogManager.shutdown ()

2003-06-20 Thread Andy McBride
(); } + lock.releaseReadLock(); return result; } On Thu, 19 Jun 2003 01:58:22 +0100 "Andy McBride" <[EMAIL PROTECTED]> wrote: > The following test class seems to hang at > LogManager.shutdown() when run with the jar produced by > the > current cvs build (1.3alp

Deadlock in ReaderWriterLock after calling LogManager.shutdown()

2003-06-18 Thread Andy McBride
The following test class seems to hang at LogManager.shutdown() when run with the jar produced by the current cvs build (1.3alpha 18/06/03). This does not occur with the released 1.2.8 jar. Further investigation points towards a deadlock in ReaderWriterLock. Printing out the existing debug lin