[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Commented] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces
From:       "Gary Gregory (JIRA)" <jira () apache ! org>
Date:       2013-07-28 17:17:49
Message-ID: JIRA.12616791.1353353669500.125938.1375031869251 () arcas
[Download RAW message or body]


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

Gary Gregory commented on LOG4J2-124:
-------------------------------------

Ah, yes, sorry for the vacation brain, I do see now that Configuration is in the Core \
module.  
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


[prev in list] [next in list] [prev in thread] [next in thread]