[
https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714667#comment-13714667
]
Ralph Goers edited comment on LOG4J2-124 at 7/21/13 8:30 AM:
-------------------------------------------------------------
I would be fine with that. But would it really be any better than
Configurator.shutdown()? I suppose it does make the application less dependent
on the implementation.
was (Author: [email protected]):
I would be fine with that. But would it really be any better than
Configurator.shutdown()?
> 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: [email protected]
For additional commands, e-mail: [email protected]
