You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Szabolcs Beki (JIRA)" <ji...@apache.org> on 2012/11/19 20:35:58 UTC
[jira] [Created] (LOG4J2-124) Gracefully stopping LogContext using
the api interfaces
Szabolcs Beki created LOG4J2-124:
------------------------------------
Summary: 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
[jira] [Commented] (LOG4J2-124) Gracefully stopping LogContext
using the api interfaces
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501573#comment-13501573 ]
Ralph Goers commented on LOG4J2-124:
------------------------------------
The LoggerContext interface currently only exposes 3 methods, getLogger, hasLogger and getExternalContext. The implementation has many more methods than this including start, stop, isStarted, getConfiguration, and reconfigure.
If the stop method were to be part of the API I am having trouble determining which of these should not. Adding getConfiguration would require making the Configuration interface part of the API, which i don't believe is appropirate. If getConfiguration isn't there then why would reconfigure be? If stop is there then why wouldn't start also be, although I can't imagine any circumstances where it would be a good idea for an application to call start.
> 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
[jira] [Commented] (LOG4J2-124) Gracefully stopping LogContext
using the api interfaces
Posted by "Gary Gregory (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501730#comment-13501730 ]
Gary Gregory commented on LOG4J2-124:
-------------------------------------
Another way to look at this is: how do I do a Log4j 1.2 LogManager.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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org