Re: Build failed in Jenkins: Log4j 2.x #1852

I'm assuming this is caused by one on my recent changes. The reasons I can think of is either the change to SimpleMessage to carry a CharSequence, or the wider lock in the file/console appenders: in the gc-free mechanism the Layout converts a LogEvent to bytes within a synchronized block. This

Re: Build failed in Jenkins: Log4j 2.x #1852

> Build timed out (after 240 minutes). Marking the build as failed. Whoa. On 7 April 2016 at 15:40, Apache Jenkins Server wrote: > See > > Changes: > > [rpopma] LOG4J2-1326 modify SimpleMessage and ReusableSimpleMessage so > they can > >

Build failed in Jenkins: Log4j 2.x #1852

See Changes: [rpopma] LOG4J2-1326 modify SimpleMessage and ReusableSimpleMessage so they can [rpopma] LOG4J2-1326 ReusableSimpleMessage test fix [rpopma] LOG4J2-1326 add methods to Logger interface that explicitly accept a [rpopma] LOG4J