[jira] [Commented] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742337#comment-14742337 ] 

Ralph Goers commented on LOG4J2-124:
------------------------------------

What are we doing with this? Do we want to modify LogManager as was proposed?

> Gracefully stopping LogContext using the api interfaces
> -------------------------------------------------------
>
>                 Key: LOG4J2-124
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-124
>             Project: Log4j 2
>          Issue Type: Question
>    Affects Versions: 2.0-beta3
>            Reporter: Szabolcs Beki
>            Priority: Minor
>
> I'm trying to gracefully close my SocketAppender before exiting the my application to avoid IOExceptions on the socket server side.  
> Currently I can make it only by using interface the org.apache.logging.log4j.core.Lifecycle interface in the Log4j2 core  : 
> ((Lifecycle) LogManager.getContext()).stop();
> I would prefer to have a cleaner solution that uses solely the Log4j-api not Log4j-core. 
> Did I overlook something or stop() on the API side really missing ? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org