On 5/20/2013 2:45 PM, Nick Williams wrote:
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Has
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/20/13 4:10 PM, Nick Williams wrote:
>>
>> On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> Nick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
>
> On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Nick,
>>
>> On 5/20/13 12:48 PM, Nick Williams wrote:
>>>
>>> On May 20, 2013,
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/20/13 12:48 PM, Nick Williams wrote:
>>
>> On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> Ni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 12:48 PM, Nick Williams wrote:
>
> On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Nick,
>>
>> On 5/19/13 11:25 AM, Nick Williams wrote:
>>> Unfortunately, requ
On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/19/13 11:25 AM, Nick Williams wrote:
>> Unfortunately, requiring users to call System.gc() before shutdown
>> for logging to work properly is no better than requiring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/19/13 11:25 AM, Nick Williams wrote:
> Unfortunately, requiring users to call System.gc() before shutdown
> for logging to work properly is no better than requiring users to
> register a listener in a web application for logging to work
>
2013/5/19 Nick Williams :
>
> On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
>
>>> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
>>> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat
>>> shutdown (memory leak, it looks
On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
>> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
>> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
>> (memory leak, it looks like)
>
>> Log4j 1 never required a list
> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
> (memory leak, it looks like)
> Log4j 1 never required a listener to be configured to be shut down
> properly when an application is un
On May 19, 2013, at 3:33 AM, Mark Thomas wrote:
> On 19/05/2013 05:57, Nick Williams wrote:
>> Can one of the very knowledgeable developers that have been
>> discussing memory leaks in the last few days (re: Possible
>> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
>> Pool
On 19/05/2013 05:57, Nick Williams wrote:
> Can one of the very knowledgeable developers that have been
> discussing memory leaks in the last few days (re: Possible
> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
> Pool and OracleTimeoutPollingThread) chime in on this Log4j 2
12 matches
Mail list logo