[LOG4J2-246] UDP socket Appender error

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta5
• Fix Version/s: 2.0-beta7
• Component/s: Appenders, Core
• Assignee: Unassigned
• Reporter: Remko Popma
• Created: 09/May/13 09:42
• Updated: 29/May/13 15:05
• Resolved: 29/May/13 05:56

Description

On 2013/05/09, at 18:34, Tomek Kaczynski <[e-mail]> 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 .

Issue Links

• is related to: LOG4J2-228 Log4j2 UDP socket configure error. Class not found org.apache.logging.log4j.core.impl.Log4jLogEvent$LogEventProxy