[jira] [Commented] (LOG4J2-246) UDP socket Appender error

e ML. > 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 >

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

e correct place to discuss enhancements to DefaultErrorHandler. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 > Project: Log4j 2

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

eant {{org.apache.logging.log4j.core.appender.DefaultErrorHandler}}. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 > Project: Log4j 2 >

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

but they aren't required to. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 > Project: Log4j 2 > Issue Type: Bug &g

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

here seems to be an opportunity for refactoring common code. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 > Project: Log4j 2 >

[jira] [Resolved] (LOG4J2-246) UDP socket Appender error

and close. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 > Project: Log4j 2 > Issue Type: Bug > Com

Re: Appender extension based on UDP socket Appender error

Hi Tomek, Before we open up the API more by using protected or public methods, I'd like to fix what we can in the code. Can you take a look at trunk and org.apache.logging.log4j.core.net.UDPSocketServerTest and the tests that are @Ignore'd there? Thank you, Gary On Mon, May 13, 2013 at 8:07 AM

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

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 >

Appender extension based on UDP socket Appender error

Hi, All Because of a bug already reported by me (LOG4J2-246), I had to write an Appender containing a fix/workaround. Obvious approach for me would be inherittance from AbstractOutputStreamAppender and overriding method append. However I could

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

vent serialization fails) sounds familiar: LOG4J2-228 is also caused by a stream header issue. > UDP socket Appender error > - > > Key: LOG4J2-246 > URL: https://issues.apache.org/jira/browse/LOG4J2-246 >

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

ing. Stack Trace : For these I am seeking help. See: commit -m "Testing LOG4J2-246: UDP socket Appender error. Needing help with UDPSocketServerTest, it is @Ignored for now." C:/svn/org/apache/log4j2/trunk/core/src/test/java/org/apache/logging/log4j/core/net/UDPSocketServerTest.java

[jira] [Updated] (LOG4J2-246) UDP socket Appender error

[ https://issues.apache.org/jira/browse/LOG4J2-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-246: Summary: UDP socket Appender error (was: Socket Appender error) > UDP socket Appender er

Re: Socket Appender error

Hi Tomek, Thank you for your bug report! We will take a look. I've created this Jira ticket to track the issue: https://issues.apache.org/jira/browse/LOG4J2-246 Best regards, Remko Sent from my iPhone On 2013/05/09, at 18:34, Tomek Kaczynski wrote: > Hi All, > > >I'm using log4j2 sinc

[jira] [Created] (LOG4J2-246) Socket Appender error

Remko Popma created LOG4J2-246: -- Summary: Socket Appender error Key: LOG4J2-246 URL: https://issues.apache.org/jira/browse/LOG4J2-246 Project: Log4j 2 Issue Type: Bug Components

Socket Appender error

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 f