The javadoc for FileDescriptor is fairly ambiguous. I’d have to look at the code, but I would guess the the FileDescriptor may just be a reference to the PrintStream. I really don’t think you can count on what it points to. I would also worry about us trying to use the FileDescriptor while the application might be writing to System.out.
Ralph > On May 24, 2016, at 10:30 AM, Remko Popma <remko.po...@gmail.com> wrote: > > > On Tuesday, May 24, 2016 at 11:27:33 PM UTC+9, Mikael Ståldal wrote: > Could we avoid that by using FileDescriptor.out / FileDescriptor.err instead > of System.out / System.err ? > > On Tue, May 24, 2016 at 4:09 PM, Matt Sicker <boa...@gmail.com <javascript:>> > wrote: > All the PrintStream.write() methods have locks. > > On 24 May 2016 at 02:56, Mikael Ståldal <mikael....@magine.com <javascript:>> > wrote: > Do we know why Console has so bad performance (compared to File)? Is this > true also if you redirect STDOUT to a file? > > and a preview of the updated performance page is here: > http://home.apache.org/~rpopma/log4j/2.6/performance.html > <http://home.apache.org/~rpopma/log4j/2.6/performance.html> > > I think these are really interesting questions, and I am curious if anyone on > this list can share their insights > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org
