Yes I run my unit test from Eclipse. I use the SpringJUnit4ClassRunner runner 
to load my application context, I don't think it registers the Spring shutdown 
hook.

-----Original Message-----
From: Remko Popma [mailto:[email protected]] 
Sent: Thursday, September 18, 2014 7:58 PM
To: Log4J Users List
Subject: Re: Ignoring log event after log4j was shut down

How are you running this unit test? (From an IDE (which one), from a Maven/Ant 
build or from the command line, ...?) Do you have any shutdown hooks and does 
logging take place inside a shutdown hook?

On Fri, Sep 19, 2014 at 1:53 AM, Mickael Marrache <[email protected]
> wrote:

> Hi,
>
>
>
> I just started to use Log4j 2 with the asynchronous logger feature, I 
> followed the guide but after a running a unit test, I always get the 
> following log entry at the end instead of the last line I expect:
>
>
>
> 2014-09-18 16:45:56,030 FATAL Ignoring log event after log4j was shut 
> down
>
>
>
> If I disable remove the Log4jContextSelector  system property, I can 
> see the last log entry instead of the error.
>
>
>
> I guess the log4j engine is shut down and therefore it ignores the log 
> entry? If yes, why it is not shut down after the test ends?
>
>
>
> Regards,
>
> Mickael
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to