logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces
Date Sun, 24 Jan 2016 18:38:40 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ralph Goers resolved LOG4J2-124.
--------------------------------
    Resolution: Fixed

Fix has been applied to master. Please verify and close.

> 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
>          Components: API
>    Affects Versions: 2.0-beta3
>            Reporter: Szabolcs Beki
>            Assignee: Ralph Goers
>            Priority: Minor
>             Fix For: 2.6
>
>
> 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


Mime
View raw message