Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Tue, 14 May 2013 13:09:15 +0000 (UTC)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12646776.1368092576154.316095.1368536955292@arcas>
In-Reply-To: <JIRA.12646776.1368092576154@arcas>
References: <JIRA.12646776.1368092576154@arcas>
Subject: [jira] [Commented] (LOG4J2-246) UDP socket Appender error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOG4J2-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657039#comment-13657039 ] 

Gary Gregory commented on LOG4J2-246:
-------------------------------------

Note that the header issue I see in the @Ignore test is affected by a timing factor. It does not always happen from the debugger.
                
> UDP socket Appender error
> -------------------------
>
>                 Key: LOG4J2-246
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-246
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders, Core
>    Affects Versions: 2.0-beta5
>            Reporter: Remko Popma
>
> On 2013/05/09, at 18:34, Tomek Kaczynski <tomek.kaczynski@gmail.com> wrote:
> Hi All,
>    I'm using log4j2 since beta4, now beta5. In general it's a cute library, but there's some bug that I've found out recently :
>    When a client code genreates a huge message ( 64k ), the underlying DatagramOutputStream fails ( UDP socket throws exception).
>   After that all following flushes fail because data buffer is not cleared upon exception.
>  So in lines
> DatagramOutputStream:91
> ----------------------------------------------------------------------
>     public synchronized void flush() throws IOException {
>         if (this.data != null && this.ds != null && this.address != null) {
>             final DatagramPacket packet = new DatagramPacket(data, data.length, address, port);
>             ds.send(packet);
>         }
>         data = null;
>     }
> --------------------------------------------------------------------------
>    
> data = null should be put in finally block or some simillar solution could be applied.
> What do you think ?
> Regards,
> Tomek
> Moreover DatagramOutputStream should check if message size is less then 64k .

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