[GitHub] logging-log4j2 issue #96: Remove empty comments and fix default buffer size ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/96 On Jul 21, 2017 21:36, "asfbot" wrote: kenneth mcfarland on dev@logging.apache.org replies: I noticed you created a JIRA for the 8012 buf size defualt. Is this something I

Re: [GitHub] logging-log4j2 issue #96: Remove empty comments and fix default buffer size ...

I noticed you created a JIRA for the 8012 buf size defualt. Is this something I should do when I'm doing something more than a typo fix? Thank you 😀 On Jul 21, 2017 2:16 PM, "kenneth mcfarland" wrote: > Sure will, new to git sorry. Still figuring it out. > > On Jul 21, 2017 2:14 PM, "garydgrego

Re: Jenkins build became unstable: Log4j 2.x #2924

It would make sense that if it is timing related that it would be erratic. Ralph > On Jul 21, 2017, at 2:26 PM, Gary Gregory wrote: > > FWIW, > > It _seems_ that errors like > https://builds.apache.org/job/Log4j%202.x/org.apache.logging.log4j$log4j-core/2924/testReport/junit/org.apache.logging

[jira] [Created] (LOGCXX-492) klduvvfkklnc

Sean P. Miller created LOGCXX-492: - Summary: klduvvfkklnc Key: LOGCXX-492 URL: https://issues.apache.org/jira/browse/LOGCXX-492 Project: Log4cxx Issue Type: Bug Reporter: Sean P.

[jira] [Closed] (LOGCXX-492) klduvvfkklnc

[ https://issues.apache.org/jira/browse/LOGCXX-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean P. Miller closed LOGCXX-492. - Resolution: Invalid Oops. > klduvvfkklnc > > > Key: LOGCXX-492 >

[jira] [Commented] (LOGCXX-491) SizeBasedRollingTest cases fail when defining LOG4CXX_MULTI_PROCESS

[ https://issues.apache.org/jira/browse/LOGCXX-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096950#comment-16096950 ] Sean P. Miller commented on LOGCXX-491: --- Original patch for this feature. > SizeBas

[GitHub] logging-log4j2 pull request #97: (doc) remove empty comments

GitHub user kpm1985 opened a pull request: https://github.com/apache/logging-log4j2/pull/97 (doc) remove empty comments sorry for all the noise. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kpm1985/logging-log4j2 cleanup Alter

[jira] [Created] (LOGCXX-491) SizeBasedRollingTest cases fail when defining LOG4CXX_MULTI_PROCESS

Sean P. Miller created LOGCXX-491: - Summary: SizeBasedRollingTest cases fail when defining LOG4CXX_MULTI_PROCESS Key: LOGCXX-491 URL: https://issues.apache.org/jira/browse/LOGCXX-491 Project: Log4cxx

[GitHub] logging-log4j2 pull request #96: Remove empty comments and fix default buffe...

Github user kpm1985 closed the pull request at: https://github.com/apache/logging-log4j2/pull/96 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Jenkins build is back to stable : Log4j 2.x #2925

See

Fwd: Jenkins build became unstable: Log4j 2.x #2924

FWIW, It _seems_ that errors like https://builds.apache.org/job/Log4j%202.x/org.apache.logging.log4j$log4j-core/2924/testReport/junit/org.apache.logging.log4j.core.appender.rolling/RollingAppenderDirectWriteWithReconfigureTest/testRollingFileAppenderWithReconfigure/ happen when the machine is bus

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

And then, you'll remove the Scala modules from the main repo's master? Gary On Fri, Jul 21, 2017 at 11:30 AM, Matt Sicker wrote: > Agreed. I'll finish this up either today or over the weekend. > > On 21 July 2017 at 07:17, Mikael Ståldal wrote: > > > Then I don't think this should block our re

Re: [GitHub] logging-log4j2 issue #96: Remove empty comments and fix default buffer size ...

Sure will, new to git sorry. Still figuring it out. On Jul 21, 2017 2:14 PM, "garydgregory" wrote: > Github user garydgregory commented on the issue: > > https://github.com/apache/logging-log4j2/pull/96 > > Thank you for your patch but I've already applied > https://github.com/apache/log

[GitHub] logging-log4j2 issue #96: Remove empty comments and fix default buffer size ...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/96 Thank you for your patch but I've already applied https://github.com/apache/logging-log4j2/pull/95 Can you merge and resubmit SVP? --- If your project is set up for it, you can reply to

[jira] [Closed] (LOG4J2-1985) Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB)

[ https://issues.apache.org/jira/browse/LOG4J2-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1985. Resolution: Fixed In Git master. > Fix default buffer size to match documentation (from 8102 to 81

[jira] [Commented] (LOG4J2-1985) Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB)

[ https://issues.apache.org/jira/browse/LOG4J2-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096879#comment-16096879 ] ASF subversion and git services commented on LOG4J2-1985: - Commit

[GitHub] logging-log4j2 issue #95: Kpm1985

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/95 Thank you for your patch. Applied to Git master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[jira] [Updated] (LOG4J2-1985) Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB)

[ https://issues.apache.org/jira/browse/LOG4J2-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1985: - Description: Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB). (was

[jira] [Updated] (LOG4J2-1985) Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB)

[ https://issues.apache.org/jira/browse/LOG4J2-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1985: - Summary: Fix default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB) (was: Fix

Jenkins build became unstable: Log4j 2.x #2924

See

[jira] [Created] (LOG4J2-1985) Fix default buffer size to match documentation (from 8102 to 8192)

Gary Gregory created LOG4J2-1985: Summary: Fix default buffer size to match documentation (from 8102 to 8192) Key: LOG4J2-1985 URL: https://issues.apache.org/jira/browse/LOG4J2-1985 Project: Log4j 2

[jira] [Commented] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096851#comment-16096851 ] Ralph Goers commented on LOG4J2-1984: - No. There has always been a max. It was 32 (an

[GitHub] logging-log4j2 pull request #96: Remove empty comments and fix default buffe...

GitHub user kpm1985 opened a pull request: https://github.com/apache/logging-log4j2/pull/96 Remove empty comments and fix default buffer size to match documentation. I have removed empty comments and changed the default buffer sizes in certain implementations to match the documenta

[jira] [Commented] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096844#comment-16096844 ] Gary Gregory commented on LOG4J2-1984: -- Hi. As soon as there is a max, some folks ar

[jira] [Closed] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1984. --- > Allow max length of StructuredDataMessage keys to be user defined > ---

[jira] [Resolved] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1984. - Resolution: Fixed Fix Version/s: 2.9 > Allow max length of StructuredDataMessage keys to b

[GitHub] logging-log4j2 pull request #95: Kpm1985

Github user kpm1985 closed the pull request at: https://github.com/apache/logging-log4j2/pull/95 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096815#comment-16096815 ] ASF subversion and git services commented on LOG4J2-1984: - Commit

[jira] [Commented] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096816#comment-16096816 ] ASF subversion and git services commented on LOG4J2-1984: - Commit

[jira] [Created] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

Ralph Goers created LOG4J2-1984: --- Summary: Allow max length of StructuredDataMessage keys to be user defined Key: LOG4J2-1984 URL: https://issues.apache.org/jira/browse/LOG4J2-1984 Project: Log4j 2

Re: [Log4j] includeNullDelimiter

The trick is to define "length": what is the size and endianness for this integer and are either configurable? I think JMeter has some code for that. But at that point, why not use the BSON for uint64 (little-endian ? Gary On Fri, Jul 21, 2017 at 12:43 PM, Matt Sicker wrote: > Exactly! I've se

Re: [Log4j] includeNullDelimiter

Exactly! I've seen similar encodings used in simple TCP framing. It should be robust enough for logging (no need for additional metadata). On 21 July 2017 at 14:39, Gary Gregory wrote: > Like Pascal strings, lengh-data-length-data... > > On Fri, Jul 21, 2017 at 11:31 AM, Matt Sicker wrote: > >

Re: [Log4j] includeNullDelimiter

Like Pascal strings, lengh-data-length-data... On Fri, Jul 21, 2017 at 11:31 AM, Matt Sicker wrote: > If the size of the message is known ahead of time, you can create a simple > framing protocol around messages as well. > > On 21 July 2017 at 07:23, Mikael Ståldal wrote: > > > I don't quite un

[GitHub] logging-log4j2 issue #95: Kpm1985

Github user kpm1985 commented on the issue: https://github.com/apache/logging-log4j2/pull/95 While reading through the PDF user guide, I have noticed on page 88 the default buffer size is indeed intended to be 8192. If this PR is dirty and needs to be cleaned up please let me know (I'

Re: [Log4j] includeNullDelimiter

If the size of the message is known ahead of time, you can create a simple framing protocol around messages as well. On 21 July 2017 at 07:23, Mikael Ståldal wrote: > I don't quite understand. > > This is something which is needed now. When you use a streaming appender > (Console, any File or So

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Agreed. I'll finish this up either today or over the weekend. On 21 July 2017 at 07:17, Mikael Ståldal wrote: > Then I don't think this should block our release. > > > On 2017-07-21 05:30, Matt Sicker wrote: > >> Logged internally: https://issues.apache.org/jira/browse/LOG4J2-1983 >> >> On 20 Ju

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096526#comment-16096526 ] Ralph Goers commented on LOG4J2-1921: - Although I'm not sure when I will have the tim

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096433#comment-16096433 ] Ajitha commented on LOG4J2-1921: Ok Ralph. In that case, we will also look for alternativ

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096364#comment-16096364 ] Ralph Goers commented on LOG4J2-1921: - OK. The Logcat appender does essentially what

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096291#comment-16096291 ] Ajitha commented on LOG4J2-1921: Refer sample configuration file: https://github.com/lou

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096193#comment-16096193 ] Ralph Goers edited comment on LOG4J2-1921 at 7/21/17 12:46 PM:

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096193#comment-16096193 ] Ralph Goers edited comment on LOG4J2-1921 at 7/21/17 12:44 PM:

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096193#comment-16096193 ] Ralph Goers commented on LOG4J2-1921: - Above you mention you use xml configuration bu

Re: [Log4j] includeNullDelimiter

I don't quite understand. This is something which is needed now. When you use a streaming appender (Console, any File or Socket with protocol=tcp/ssl), the layout needs to provide some way to delimit log events. On 2017-07-20 22:28, Matt Sicker wrote: I'm not a fan of the null termination a

Re: [Log4j] log4j-server

The repository is not ready for release. On 2017-07-20 22:26, Matt Sicker wrote: Is the repo ready for release? I can probably be the RM for it. These smaller modules take quite a bit less time to make RCs for than the main repo (which is why we're working on splitting it up in the first place)

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Then I don't think this should block our release. On 2017-07-21 05:30, Matt Sicker wrote: Logged internally: https://issues.apache.org/jira/browse/LOG4J2-1983 On 20 July 2017 at 22:22, Matt Sicker wrote: I did find this Scala issue: https://github.com/scala/bug/issues/10417 On 20 July 2017

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095974#comment-16095974 ] Ajitha edited comment on LOG4J2-1921 at 7/21/17 8:50 AM: - Friends

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095974#comment-16095974 ] Ajitha commented on LOG4J2-1921: Friends, I want to give a background on the requirement