logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-1238) org.apache.logging.log4j.core.net.TcpSocketManager and other classes does not report internal exceptions to the status logger
Date Fri, 01 Jan 2016 01:47:39 GMT

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

Gary Gregory closed LOG4J2-1238.
--------------------------------
    Resolution: Fixed

In Git master.

> org.apache.logging.log4j.core.net.TcpSocketManager and other classes does not report
internal exceptions to the status logger
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1238
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1238
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5
>         Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
> Maven home: E:\Java\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>             Fix For: 2.5.1
>
>
> The class org.apache.logging.log4j.core.net.TcpSocketManager and other classes does not
report internal exceptions to the status logger. This makes it much harder to debug than it
has to be.



--
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