Jon, Thanks for picking this up. It is definitely a bug. I can fix it but perhaps you want to have a go at it.
Conor > -----Original Message----- > From: Jon Skeet [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 19 February 2002 6:20 AM > To: Ant Developers List > Subject: RE: Next set of JavaDoc patches > > > > >Identified thread-safety problem in DemuxOutputStream (look for XXX) > > > > Interesting,. There is a bug entry about odd output running <java> in > > <parallel>, but like most thread problems, replication is a > > dog. maybe this was the cause. > > I'd be thrilled if what I was doing turned out to be immediately useful :) > > Just for my own reference if I decide to go back and track this: > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4400 > > Reproducing this could be interesting, certainly - you need to > *happen* to get a thread context switch between write ('\r') and > write ('\n') in one thread *and* the other thread get both '\r' > and '\n' before the other thread gets in again. On the other > hand, putting some kind of logging (and conditional sleeping, > possibly) in the potentially problematic bit of code could make > it more easily reproducible. > > I can't actually see why we'd get this behaviour though - I would > have thought the streams would get processed eventually when they > were flushed/closed. > > Jon > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
