You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:29:03 UTC

[jira] [Updated] (LOG4NET-471) RemotingAppender does register a TcpChannel under the default name 'tcp'

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

Ralph Goers updated LOG4NET-471:
--------------------------------

LOG4NET is now dormant.  

> RemotingAppender does register a TcpChannel under the default name 'tcp'
> ------------------------------------------------------------------------
>
>                 Key: LOG4NET-471
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-471
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.13
>            Reporter: Manuel Peelen
>            Priority: Major
>              Labels: easyfix
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> I am under the impression that RemotingAppender does register a TcpChannel under the default name 'tcp'. As a result they cannot be used in an application which is itself trying to register a TcpChannel using the default name. Otherwise an Exception will be raised "The channel 'tcp' is already registered".
> Of course this can also be solved by changing the application. However this is not always an option.
> I would propose changing the TcpChannel name to something like 'log4net', which is unlikely to be used by a third party. I imagine this to be a small change.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)