You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Mariano Gonzalez <ma...@gmail.com> on 2014/12/02 18:46:19 UTC
ArrayIndexOutOfBoundsException with RollingFileApender
Hello,
I'm progamatically creating an appender with the following code:
private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
private RollingFileAppender createRollingFileAppender(String logFilePath,
String filePattern, String appenderName, Configuration configuration)
{
TriggeringPolicy triggeringPolicy =
TimeBasedTriggeringPolicy.createPolicy("1", "true");
RolloverStrategy rolloverStrategy =
DefaultRolloverStrategy.createStrategy("30", "1", null,
String.valueOf(Deflater.NO_COMPRESSION), configuration);
return RollingFileAppender.createAppender(logFilePath,
logFilePath + filePattern,
"true",
appenderName,
"true",
null, null,
triggeringPolicy,
rolloverStrategy,
createLayout(configuration),
null, null, null, null,
configuration);
}
private Layout<? extends Serializable> createLayout(Configuration
configuration)
{
return PatternLayout.createLayout(PATTERN_LAYOUT, configuration, null,
null, true, false, null, null);
}
Sometimes, not always, when an exception is thrown I end up seeing the
following error:
2014-12-02 14:36:52,092 ERROR An exception occurred processing Appender
defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
at
org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
at
org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
at
org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
at
org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
at
org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
at
org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
at
org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
at
org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
at
org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
at
org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
at
org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
at
org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
at
org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
I noticed that it doesn't happen for every exception, but when it does
happen, it happens consistently. I also noticed that it's the causedTrace
array the one that usually falls short. Is this a known issue? Any way I
can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
Thanks you!
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Mariano Gonzalez <ma...@gmail.com>.
Hello Gary,
What I meant by mandatory is that the only way of getting the fix was
upgrading to 2.1. I have code freeze on Thursday so I was trying to avoid a
last minute dependency change, but it seems like that's just the way it is.
Of course I can always fork the project but that seems overkill just for
this.
Thank you for your help!
On Tue, Dec 2, 2014 at 3:29 PM, Gary Gregory <ga...@gmail.com> wrote:
> Good, I am glad the current version work for you.
>
> Why would it be mandatory to upgrade? Only you can decide that ;-) The
> released versions will live in the Maven repository "forever".
>
> That part of the code was probably changed as part of fixing LOG4J2-832.
>
> Gary
>
> On Tue, Dec 2, 2014 at 1:16 PM, Mariano Gonzalez <
> mariano.l.gonzalez@gmail.com> wrote:
>
> > Hello Gary,
> >
> > Thank you for your response. 2.1 does fix the issue, is it mandatory to
> > upgrade? was it a logic error or just some setting I could force into my
> > current version?
> >
> > Thanks
> >
> > On Tue, Dec 2, 2014 at 3:07 PM, Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> > > FYI: the stack trace does not match with our current git master level
> > > sources which is not surprising since we are evolving and fixing
> things.
> > >
> > > If you had a little program that could reproduce the issue that would
> be
> > > great.
> > >
> > > You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
> > > from sources too).
> > >
> > > Gary
> > >
> > > On Tue, Dec 2, 2014 at 12:57 PM, Gary Gregory <ga...@gmail.com>
> > > wrote:
> > >
> > > > Can you try version 2.1?
> > > >
> > > > Gary
> > > >
> > > > On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
> > > > mariano.l.gonzalez@gmail.com> wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> I'm progamatically creating an appender with the following code:
> > > >>
> > > >> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c:
> %m%n";
> > > >>
> > > >> private RollingFileAppender createRollingFileAppender(String
> > > logFilePath,
> > > >> String filePattern, String appenderName, Configuration
> configuration)
> > > >> {
> > > >> TriggeringPolicy triggeringPolicy =
> > > >> TimeBasedTriggeringPolicy.createPolicy("1", "true");
> > > >> RolloverStrategy rolloverStrategy =
> > > >> DefaultRolloverStrategy.createStrategy("30", "1", null,
> > > >> String.valueOf(Deflater.NO_COMPRESSION), configuration);
> > > >>
> > > >> return RollingFileAppender.createAppender(logFilePath,
> > > >> logFilePath + filePattern,
> > > >> "true",
> > > >> appenderName,
> > > >> "true",
> > > >> null, null,
> > > >> triggeringPolicy,
> > > >> rolloverStrategy,
> > > >> createLayout(configuration),
> > > >> null, null, null, null,
> > > >> configuration);
> > > >> }
> > > >>
> > > >> private Layout<? extends Serializable> createLayout(Configuration
> > > >> configuration)
> > > >> {
> > > >> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration,
> > > null,
> > > >> null, true, false, null, null);
> > > >> }
> > > >>
> > > >> Sometimes, not always, when an exception is thrown I end up seeing
> the
> > > >> following error:
> > > >>
> > > >> 2014-12-02 14:36:52,092 ERROR An exception occurred processing
> > Appender
> > > >> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
> > > >>
> > > >> at
> > > >>
> > com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > >>
> > > >> at
> > > >>
> > > >>
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > >>
> > > >> at java.lang.Thread.run(Thread.java:745)
> > > >>
> > > >>
> > > >> I noticed that it doesn't happen for every exception, but when it
> does
> > > >> happen, it happens consistently. I also noticed that it's the
> > > causedTrace
> > > >> array the one that usually falls short. Is this a known issue? Any
> > way I
> > > >> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
> > > >>
> > > >>
> > > >> Thanks you!
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > > > Java Persistence with Hibernate, Second Edition
> > > > <http://www.manning.com/bauer3/>
> > > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > > > Spring Batch in Action <http://www.manning.com/templier/>
> > > > Blog: http://garygregory.wordpress.com
> > > > Home: http://garygregory.com/
> > > > Tweet! http://twitter.com/GaryGregory
> > > >
> > >
> > >
> > >
> > > --
> > > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > > Java Persistence with Hibernate, Second Edition
> > > <http://www.manning.com/bauer3/>
> > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > > Spring Batch in Action <http://www.manning.com/templier/>
> > > Blog: http://garygregory.wordpress.com
> > > Home: http://garygregory.com/
> > > Tweet! http://twitter.com/GaryGregory
> > >
> >
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Gary Gregory <ga...@gmail.com>.
Good, I am glad the current version work for you.
Why would it be mandatory to upgrade? Only you can decide that ;-) The
released versions will live in the Maven repository "forever".
That part of the code was probably changed as part of fixing LOG4J2-832.
Gary
On Tue, Dec 2, 2014 at 1:16 PM, Mariano Gonzalez <
mariano.l.gonzalez@gmail.com> wrote:
> Hello Gary,
>
> Thank you for your response. 2.1 does fix the issue, is it mandatory to
> upgrade? was it a logic error or just some setting I could force into my
> current version?
>
> Thanks
>
> On Tue, Dec 2, 2014 at 3:07 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > FYI: the stack trace does not match with our current git master level
> > sources which is not surprising since we are evolving and fixing things.
> >
> > If you had a little program that could reproduce the issue that would be
> > great.
> >
> > You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
> > from sources too).
> >
> > Gary
> >
> > On Tue, Dec 2, 2014 at 12:57 PM, Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> > > Can you try version 2.1?
> > >
> > > Gary
> > >
> > > On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
> > > mariano.l.gonzalez@gmail.com> wrote:
> > >
> > >> Hello,
> > >>
> > >> I'm progamatically creating an appender with the following code:
> > >>
> > >> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
> > >>
> > >> private RollingFileAppender createRollingFileAppender(String
> > logFilePath,
> > >> String filePattern, String appenderName, Configuration configuration)
> > >> {
> > >> TriggeringPolicy triggeringPolicy =
> > >> TimeBasedTriggeringPolicy.createPolicy("1", "true");
> > >> RolloverStrategy rolloverStrategy =
> > >> DefaultRolloverStrategy.createStrategy("30", "1", null,
> > >> String.valueOf(Deflater.NO_COMPRESSION), configuration);
> > >>
> > >> return RollingFileAppender.createAppender(logFilePath,
> > >> logFilePath + filePattern,
> > >> "true",
> > >> appenderName,
> > >> "true",
> > >> null, null,
> > >> triggeringPolicy,
> > >> rolloverStrategy,
> > >> createLayout(configuration),
> > >> null, null, null, null,
> > >> configuration);
> > >> }
> > >>
> > >> private Layout<? extends Serializable> createLayout(Configuration
> > >> configuration)
> > >> {
> > >> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration,
> > null,
> > >> null, true, false, null, null);
> > >> }
> > >>
> > >> Sometimes, not always, when an exception is thrown I end up seeing the
> > >> following error:
> > >>
> > >> 2014-12-02 14:36:52,092 ERROR An exception occurred processing
> Appender
> > >> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
> > >>
> > >> at
> > >>
> > >>
> >
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
> > >>
> > >> at
> > >>
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> > >>
> > >> at
> > >>
> > >>
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > >>
> > >> at
> > >>
> > >>
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > >>
> > >> at java.lang.Thread.run(Thread.java:745)
> > >>
> > >>
> > >> I noticed that it doesn't happen for every exception, but when it does
> > >> happen, it happens consistently. I also noticed that it's the
> > causedTrace
> > >> array the one that usually falls short. Is this a known issue? Any
> way I
> > >> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
> > >>
> > >>
> > >> Thanks you!
> > >>
> > >
> > >
> > >
> > > --
> > > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > > Java Persistence with Hibernate, Second Edition
> > > <http://www.manning.com/bauer3/>
> > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > > Spring Batch in Action <http://www.manning.com/templier/>
> > > Blog: http://garygregory.wordpress.com
> > > Home: http://garygregory.com/
> > > Tweet! http://twitter.com/GaryGregory
> > >
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition
> > <http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Mariano Gonzalez <ma...@gmail.com>.
Hello Gary,
Thank you for your response. 2.1 does fix the issue, is it mandatory to
upgrade? was it a logic error or just some setting I could force into my
current version?
Thanks
On Tue, Dec 2, 2014 at 3:07 PM, Gary Gregory <ga...@gmail.com> wrote:
> FYI: the stack trace does not match with our current git master level
> sources which is not surprising since we are evolving and fixing things.
>
> If you had a little program that could reproduce the issue that would be
> great.
>
> You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
> from sources too).
>
> Gary
>
> On Tue, Dec 2, 2014 at 12:57 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > Can you try version 2.1?
> >
> > Gary
> >
> > On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
> > mariano.l.gonzalez@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I'm progamatically creating an appender with the following code:
> >>
> >> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
> >>
> >> private RollingFileAppender createRollingFileAppender(String
> logFilePath,
> >> String filePattern, String appenderName, Configuration configuration)
> >> {
> >> TriggeringPolicy triggeringPolicy =
> >> TimeBasedTriggeringPolicy.createPolicy("1", "true");
> >> RolloverStrategy rolloverStrategy =
> >> DefaultRolloverStrategy.createStrategy("30", "1", null,
> >> String.valueOf(Deflater.NO_COMPRESSION), configuration);
> >>
> >> return RollingFileAppender.createAppender(logFilePath,
> >> logFilePath + filePattern,
> >> "true",
> >> appenderName,
> >> "true",
> >> null, null,
> >> triggeringPolicy,
> >> rolloverStrategy,
> >> createLayout(configuration),
> >> null, null, null, null,
> >> configuration);
> >> }
> >>
> >> private Layout<? extends Serializable> createLayout(Configuration
> >> configuration)
> >> {
> >> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration,
> null,
> >> null, true, false, null, null);
> >> }
> >>
> >> Sometimes, not always, when an exception is thrown I end up seeing the
> >> following error:
> >>
> >> 2014-12-02 14:36:52,092 ERROR An exception occurred processing Appender
> >> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
> >>
> >> at
> >>
> >>
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
> >>
> >> at
> >> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> >>
> >> at
> >>
> >>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> >>
> >> at
> >>
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> >>
> >> at java.lang.Thread.run(Thread.java:745)
> >>
> >>
> >> I noticed that it doesn't happen for every exception, but when it does
> >> happen, it happens consistently. I also noticed that it's the
> causedTrace
> >> array the one that usually falls short. Is this a known issue? Any way I
> >> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
> >>
> >>
> >> Thanks you!
> >>
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition
> > <http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Gary Gregory <ga...@gmail.com>.
It would also help to see the stack trace being logged.
Gary
On Tue, Dec 2, 2014 at 1:07 PM, Gary Gregory <ga...@gmail.com> wrote:
> FYI: the stack trace does not match with our current git master level
> sources which is not surprising since we are evolving and fixing things.
>
> If you had a little program that could reproduce the issue that would be
> great.
>
> You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
> from sources too).
>
> Gary
>
> On Tue, Dec 2, 2014 at 12:57 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
>> Can you try version 2.1?
>>
>> Gary
>>
>> On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
>> mariano.l.gonzalez@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I'm progamatically creating an appender with the following code:
>>>
>>> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
>>>
>>> private RollingFileAppender createRollingFileAppender(String logFilePath,
>>> String filePattern, String appenderName, Configuration configuration)
>>> {
>>> TriggeringPolicy triggeringPolicy =
>>> TimeBasedTriggeringPolicy.createPolicy("1", "true");
>>> RolloverStrategy rolloverStrategy =
>>> DefaultRolloverStrategy.createStrategy("30", "1", null,
>>> String.valueOf(Deflater.NO_COMPRESSION), configuration);
>>>
>>> return RollingFileAppender.createAppender(logFilePath,
>>> logFilePath + filePattern,
>>> "true",
>>> appenderName,
>>> "true",
>>> null, null,
>>> triggeringPolicy,
>>> rolloverStrategy,
>>> createLayout(configuration),
>>> null, null, null, null,
>>> configuration);
>>> }
>>>
>>> private Layout<? extends Serializable> createLayout(Configuration
>>> configuration)
>>> {
>>> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration,
>>> null,
>>> null, true, false, null, null);
>>> }
>>>
>>> Sometimes, not always, when an exception is thrown I end up seeing the
>>> following error:
>>>
>>> 2014-12-02 14:36:52,092 ERROR An exception occurred processing Appender
>>> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
>>>
>>> at
>>>
>>> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
>>>
>>> at
>>> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
>>>
>>> at
>>>
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>>
>>> at
>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>>
>>> I noticed that it doesn't happen for every exception, but when it does
>>> happen, it happens consistently. I also noticed that it's the causedTrace
>>> array the one that usually falls short. Is this a known issue? Any way I
>>> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
>>>
>>>
>>> Thanks you!
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Gary Gregory <ga...@gmail.com>.
FYI: the stack trace does not match with our current git master level
sources which is not surprising since we are evolving and fixing things.
If you had a little program that could reproduce the issue that would be
great.
You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
from sources too).
Gary
On Tue, Dec 2, 2014 at 12:57 PM, Gary Gregory <ga...@gmail.com>
wrote:
> Can you try version 2.1?
>
> Gary
>
> On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
> mariano.l.gonzalez@gmail.com> wrote:
>
>> Hello,
>>
>> I'm progamatically creating an appender with the following code:
>>
>> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
>>
>> private RollingFileAppender createRollingFileAppender(String logFilePath,
>> String filePattern, String appenderName, Configuration configuration)
>> {
>> TriggeringPolicy triggeringPolicy =
>> TimeBasedTriggeringPolicy.createPolicy("1", "true");
>> RolloverStrategy rolloverStrategy =
>> DefaultRolloverStrategy.createStrategy("30", "1", null,
>> String.valueOf(Deflater.NO_COMPRESSION), configuration);
>>
>> return RollingFileAppender.createAppender(logFilePath,
>> logFilePath + filePattern,
>> "true",
>> appenderName,
>> "true",
>> null, null,
>> triggeringPolicy,
>> rolloverStrategy,
>> createLayout(configuration),
>> null, null, null, null,
>> configuration);
>> }
>>
>> private Layout<? extends Serializable> createLayout(Configuration
>> configuration)
>> {
>> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration, null,
>> null, true, false, null, null);
>> }
>>
>> Sometimes, not always, when an exception is thrown I end up seeing the
>> following error:
>>
>> 2014-12-02 14:36:52,092 ERROR An exception occurred processing Appender
>> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
>>
>> at
>>
>> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
>>
>> at
>>
>> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
>>
>> at
>>
>> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
>>
>> at
>>
>> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
>>
>> at
>>
>> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
>>
>> at
>>
>> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
>>
>> at
>>
>> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
>>
>> at
>>
>> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
>>
>> at
>>
>> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
>>
>> at
>>
>> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
>>
>> at
>>
>> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
>>
>> at
>>
>> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
>>
>> at
>>
>> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
>>
>> at
>>
>> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
>>
>> at
>> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
>>
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> I noticed that it doesn't happen for every exception, but when it does
>> happen, it happens consistently. I also noticed that it's the causedTrace
>> array the one that usually falls short. Is this a known issue? Any way I
>> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
>>
>>
>> Thanks you!
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: ArrayIndexOutOfBoundsException with RollingFileApender
Posted by Gary Gregory <ga...@gmail.com>.
Can you try version 2.1?
Gary
On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
mariano.l.gonzalez@gmail.com> wrote:
> Hello,
>
> I'm progamatically creating an appender with the following code:
>
> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
>
> private RollingFileAppender createRollingFileAppender(String logFilePath,
> String filePattern, String appenderName, Configuration configuration)
> {
> TriggeringPolicy triggeringPolicy =
> TimeBasedTriggeringPolicy.createPolicy("1", "true");
> RolloverStrategy rolloverStrategy =
> DefaultRolloverStrategy.createStrategy("30", "1", null,
> String.valueOf(Deflater.NO_COMPRESSION), configuration);
>
> return RollingFileAppender.createAppender(logFilePath,
> logFilePath + filePattern,
> "true",
> appenderName,
> "true",
> null, null,
> triggeringPolicy,
> rolloverStrategy,
> createLayout(configuration),
> null, null, null, null,
> configuration);
> }
>
> private Layout<? extends Serializable> createLayout(Configuration
> configuration)
> {
> return PatternLayout.createLayout(PATTERN_LAYOUT, configuration, null,
> null, true, false, null, null);
> }
>
> Sometimes, not always, when an exception is thrown I end up seeing the
> following error:
>
> 2014-12-02 14:36:52,092 ERROR An exception occurred processing Appender
> defaultFileAppender java.lang.ArrayIndexOutOfBoundsException: 53
>
> at
>
> org.apache.logging.log4j.core.impl.ThrowableProxy.formatElements(ThrowableProxy.java:227)
>
> at
>
> org.apache.logging.log4j.core.impl.ThrowableProxy.getExtendedStackTraceAsString(ThrowableProxy.java:401)
>
> at
>
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:72)
>
> at
>
> org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36)
>
> at
>
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:189)
>
> at
>
> org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:53)
>
> at
>
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:52)
>
> at
>
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:104)
>
> at
>
> org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:86)
>
> at
>
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:97)
>
> at
>
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:428)
>
> at
>
> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:118)
>
> at
>
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:222)
>
> at
>
> org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigHelper.java:207)
>
> at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
>
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>
> at java.lang.Thread.run(Thread.java:745)
>
>
> I noticed that it doesn't happen for every exception, but when it does
> happen, it happens consistently. I also noticed that it's the causedTrace
> array the one that usually falls short. Is this a known issue? Any way I
> can get a fix? Maybe with a different layout? I'm using log4j 2.0.2
>
>
> Thanks you!
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory