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 Tomek Sztelak <ts...@gmail.com> on 2014/11/21 10:34:35 UTC
Log4j 2.1 and compilation memory usage
Hello
We just updated log4j from 2.0-beta9 to 2.1 and memory consumtion during
compilation of our application increased about 300-400MB causing
OutOfMemory on same machines.
Any idea what can cause this?
Best regards.
Re: Log4j 2.1 and compilation memory usage
Posted by Ralph Goers <ra...@dslextreme.com>.
I believe the annotation processor was also added between those releases. Do you have your own Log4j plugins? I am not sure if the annotation processor can be configured to ignore packages.
Ralph
> On Nov 22, 2014, at 5:45 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> Is the Log4j version the ONLY thing that changed?
>
> I am guessing that more dependencies are being brought in perhaps.
>
> You can run Maven with verbose/debug output and see what classpath the
> compiler is using in both cases.
>
> Gary
>
> On Fri, Nov 21, 2014 at 4:34 AM, Tomek Sztelak <ts...@gmail.com> wrote:
>
>> Hello
>>
>> We just updated log4j from 2.0-beta9 to 2.1 and memory consumtion during
>> compilation of our application increased about 300-400MB causing
>> OutOfMemory on same machines.
>> Any idea what can cause this?
>>
>> Best regards.
>>
>
>
>
> --
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Log4j 2.1 and compilation memory usage
Posted by Gary Gregory <ga...@gmail.com>.
Is the Log4j version the ONLY thing that changed?
I am guessing that more dependencies are being brought in perhaps.
You can run Maven with verbose/debug output and see what classpath the
compiler is using in both cases.
Gary
On Fri, Nov 21, 2014 at 4:34 AM, Tomek Sztelak <ts...@gmail.com> wrote:
> Hello
>
> We just updated log4j from 2.0-beta9 to 2.1 and memory consumtion during
> compilation of our application increased about 300-400MB causing
> OutOfMemory on same machines.
> Any idea what can cause this?
>
> Best regards.
>
--
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