Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

live without the monitoring since the xml is packaged within a > jar anyway. But that might change in the future. > > Regards, > Veit > > > > > Gesendet: Freitag, 18. Dezember 2015 um 02:10 Uhr > Von: "Ralph Goers" <ralph.go...@dslextr

Aw: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

reitag, 18. Dezember 2015 um 17:35 Uhr Von: "Ralph Goers" <ralph.go...@dslextreme.com> An: "Log4J Users List" <log4j-user@logging.apache.org> Betreff: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap Thanks. I’ll take a look at that. The scheduler

Aw: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

extreme.com> An: "Log4J Users List" <log4j-user@logging.apache.org> Betreff: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap Although the configuration format has changed, it shouldn’t be too difficult to figure out how to create a similar configuration in Log4j 2. I

still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

Hi. We're developing a Jersey 2(.22.1) REST service with JDK8, log4j 1.2.16 and SLF4J 1.7.7 using Tomcat 8.0.23. Recently I stumbled across the problem mentioned here: https://bz.apache.org/bugzilla/show_bug.cgi?id=50486 Where Tomcat complains about left behind ThreadLocalMaps. I updated to

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

Is there any chance you can update your app to Log4j 2.5 using our 1.2 bridge? Gary On Thu, Dec 17, 2015 at 9:36 AM, Veit Guna wrote: > Hi. > > We're developing a Jersey 2(.22.1) REST service with JDK8, log4j 1.2.16 > and SLF4J 1.7.7 using Tomcat 8.0.23. > > Recently I

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

t.g...@gmx.de> To: log4j-user@logging.apache.org Sent: Thursday, December 17, 2015 12:36 PM Subject: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap Hi. We're developing a Jersey 2(.22.1) REST service with JDK8, log4j 1.2.16 and SLF4J 1.7.7 using Tomcat 8.0.23. Recently I st

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

.5 because my code has to > run under Java 1.6. I suspect that is the case with a lot of developers who > deploy on WebSphere or WebLogic. > > > > From: Veit Guna <veit.g...@gmx.de> > To: log4j-user@logging.apache.org > Sent: Thursday, Dece

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

Hi Gary. I can give it a try tomorrow. Has the log4j.xml format been changed? Or does the bridge handle that too? Am 17. Dezember 2015 19:16:24 MEZ, schrieb Gary Gregory : >Is there any chance you can update your app to Log4j 2.5 using our 1.2 >bridge? > >Gary > >On

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

code has to >> run under Java 1.6. I suspect that is the case with a lot of developers who >> deploy on WebSphere or WebLogic. >> >> >> >> From: Veit Guna <veit.g...@gmx.de> >> To: log4j-user@logging.apache.org >> Sent: Thursday, Decembe

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

The configuration format has changed. It had to due to the plugin system that log4j 2 uses and because there are many new features and so many things were implemented differently. Ralph > On Dec 17, 2015, at 2:29 PM, Veit Guna wrote: > > Hi Gary. > > I can give it a try

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

it some other way. From: Gary Gregory <garydgreg...@gmail.com> To: Dave Glasser <dglas...@pobox.com>; Log4J Users List <log4j-user@logging.apache.org> Sent: Thursday, December 17, 2015 3:16 PM Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

> To: Dave Glasser <dglas...@pobox.com>; Log4J Users List < > log4j-user@logging.apache.org> > Sent: Thursday, December 17, 2015 3:16 PM > Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap > > Hello, > > Log4j 1 has reached EOL. For Java 6

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

...@gmail.com> >  To: Dave Glasser <dglas...@pobox.com>; Log4J Users List < > log4j-user@logging.apache.org> >  Sent: Thursday, December 17, 2015 3:16 PM >  Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap > > Hello, > > Log4j 1 ha

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

.@gmail.com> > To: Log4J Users List <log4j-user@logging.apache.org>; Dave Glasser < > dglas...@pobox.com> > Sent: Thursday, December 17, 2015 6:32 PM > Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap > > Can you list which bugs in JIRA you'd like

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

Although the configuration format has changed, it shouldn’t be too difficult to figure out how to create a similar configuration in Log4j 2. If you have any problems at all please ask. We will be happy to help with that. Ralph > On Dec 17, 2015, at 2:29 PM, Veit Guna wrote:

Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

ure. > > > > > > > > From: Gary Gregory <garydgreg...@gmail.com> > > To: Log4J Users List <log4j-user@logging.apache.org>; Dave Glasser < > > dglas...@pobox.com> > > Sent: Thursday, December 17, 2015 6:32 PM > > Subject: Re: stil