[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803242#comment-15803242 ] A commented on LOG4J2-1768: --- Here is SO link where Remko asked to raise this on the Log4j2 JIRA

[jira] [Created] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

A created LOG4J2-1768: - Summary: MDC.clear() is broken in Log4j-1_2-api = 2.4 Key: LOG4J2-1768 URL: https://issues.apache.org/jira/browse/LOG4J2-1768 Project: Log4j 2 Issue Type: Bug Affects Versions

[jira] [Comment Edited] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803015#comment-15803015 ] Ralph Goers edited comment on LOG4J2-1713 at 1/6/17 12:31 AM: -

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803015#comment-15803015 ] Ralph Goers commented on LOG4J2-1713: - If you have log4j jars in both tomcat/lib and

Re: Documentation format

On Thu, Jan 5, 2017 at 3:14 PM, Matt Sicker wrote: > GitHub supports adoc; it's why I used it. https://github.com/apache/ > logging-log4j2/blob/master/BUILDING.adoc > Nice, I learn new things everyday. Gary > > On 5 January 2017 at 17:03, Gary Gregory wrote: > >> Hm, we will still have MD fi

Re: org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields

Can some sort of generic plugin similar to the ColumnMapping one I just added be used here? Allow layouts within markup layouts. Seems kind of meta, so it might require some more design. On 5 January 2017 at 17:10, Remko Popma wrote: > There is an outstanding request for the JSON layout to show

Re: Documentation format

GitHub supports adoc; it's why I used it. https://github.com/apache/logging-log4j2/blob/master/BUILDING.adoc On 5 January 2017 at 17:03, Gary Gregory wrote: > Hm, we will still have MD files for GitHub unless we have some tooling to > convert ADOC to MD. Thoughts? > > Gary > > On Thu, Jan 5, 201

Re: org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields

There is an outstanding request for the JSON layout to show a formatted timestamp instead of (or in addition to) the current millis since epoch long. Could this AdditionalFields feature be used for that? Sent from my iPhone > On Jan 6, 2017, at 7:40, Gary Gregory wrote: > > - HTML could, JS

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802809#comment-15802809 ] Remko Popma commented on LOG4J2-1724: - (Haven't looked at patch.) Is the documentatio

Re: Documentation format

Hm, we will still have MD files for GitHub unless we have some tooling to convert ADOC to MD. Thoughts? Gary On Thu, Jan 5, 2017 at 2:53 PM, Matt Sicker wrote: > Where is .txt? I see .xml which is some sort of HTML extension format. > > I have more experience with markdown, but asciidoc seems t

Re: Documentation format

Where is .txt? I see .xml which is some sort of HTML extension format. I have more experience with markdown, but asciidoc seems to be more commonly used for actual documentation due to its feature set. I was thinking of suggesting that we convert our HTML manual into one of those formats. On 5 Ja

Re: org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields

- HTML could, JSON could, XML could, YAML could (these are all pretty open ended) - Then I can recall if Syslog has such an allowance, I recall someone asking about that, perhaps in the message itself. - Does seem to make sense for CSV for example. Gary On Thu, Jan 5, 2017 at 2:34 PM, Remko Pop

Re: org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields

Which Layouts actually support additional fields? I wouldn't pull it up until there's a need. Sent from my iPhone > On Jan 6, 2017, at 4:08, Gary Gregory wrote: > > I think we should pull up > org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields to > the superclass so it

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802528#comment-15802528 ] Kurt Seidel commented on LOG4J2-1713: - Yes I noticed that when I researched that erro

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still rolls over based on the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Summary: when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still rolls over based on t

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Description: I have log4j2.json config as below, with SizeBasedTriggeringPolicy as 1MB. Its a web app

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Description: I have log4j2.json config as below, with SizeBasedTriggeringPolicy as 1MB. Its a web app

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Summary: when SizeBasedTriggeringPolicy value is changed on the fly, log4j2 still picks up the older va

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Environment: java-1.8.0-ibm-1.8.0.3.20-1, log4j2 2.5 was: IBM Websphere, java-1.8.0-ibm-1.8.0.3.20

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Description: I have log4j2.json config as below, with SizeBasedTriggeringPolicy as 1MB. Its a web app

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Affects Version/s: (was: 2.6.2) > when SizeBasedTriggeringPolicy value is changed, log4j2 still pic

[jira] [Updated] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value

[ https://issues.apache.org/jira/browse/LOG4J2-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prayagupd updated LOG4J2-1767: -- Description: (was: When I am testing my logs in IBM server with websphere 8, I see multiple log fil

[jira] [Created] (LOG4J2-1767) when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value

prayagupd created LOG4J2-1767: - Summary: when SizeBasedTriggeringPolicy value is changed, log4j2 still picks up the older value Key: LOG4J2-1767 URL: https://issues.apache.org/jira/browse/LOG4J2-1767 Proj

[jira] [Commented] (LOG4J2-1754) Multiple log files being created for rolling log4j2 conf in IBM Websphere

[ https://issues.apache.org/jira/browse/LOG4J2-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802481#comment-15802481 ] prayagupd commented on LOG4J2-1754: --- Thanks Ralph, will do that and see. > Multiple lo

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802454#comment-15802454 ] Gary Gregory commented on LOG4J2-1713: -- I've not gone through your whole post but er

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802416#comment-15802416 ] Kurt Seidel commented on LOG4J2-1713: - Gary - thanks for the tip. I was hopeful that

Re: Documentation format

AsciiDoc? Really? We need to settle on AsciiDoc or MD. Pick one. MD seems to be quite popular these days. Gary On Thu, Jan 5, 2017 at 8:58 AM, Mikael Ståldal wrote: > Since Matt's recent committ, we now have three different documentation > formats: .txt, .md and .adoc > > Should we try to be mo

Jenkins build is still unstable: Log4j 2.x #2570

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields

I think we should pull up org.apache.logging.log4j.core.layout.GelfLayout.Builder.additionalFields to the superclass so it can be used in any layout (that allows for extra fields). Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edi

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802120#comment-15802120 ] Mikael Ståldal commented on LOG4J2-1724: I have done it. > Using variables in Ge

[jira] [Resolved] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1724. Resolution: Fixed Fix Version/s: 2.8 In Git master, please verify and close. > Usin

Jenkins build became unstable: Log4j 2.x #2569

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Documentation format

Since Matt's recent committ, we now have three different documentation formats: .txt, .md and .adoc Should we try to be more consistent? Maybe choose one of Markdown and AsciiDoc and convert to it? I am used to Markdown, but I can be convinced to use AsciiDoc instead if it has clear advantages.

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801807#comment-15801807 ] Mikael Ståldal commented on LOG4J2-1724: I have now fixed builders. The patched s

[jira] [Commented] (LOG4J2-1653) CronTriggeringPolicy uses wrong naming and produces NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801716#comment-15801716 ] Georg Friedrich commented on LOG4J2-1653: - I see. I will give you an update on M