[jira] [Updated] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1474: Fix Version/s: 2.7 > CronTriggeringPolicy raise exception and fail to rollover log file when >

[jira] [Commented] (LOG4J2-1476) New line is not appending in file logs

[ https://issues.apache.org/jira/browse/LOG4J2-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393236#comment-15393236 ] Remko Popma commented on LOG4J2-1476: - I can see that your pattern layout ends with "%n%n%n", so you

[jira] [Comment Edited] (LOG4J2-1476) New line is not appending in file logs

[ https://issues.apache.org/jira/browse/LOG4J2-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393178#comment-15393178 ] Remko Popma edited comment on LOG4J2-1476 at 7/26/16 5:09 AM: -- This is the

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393206#comment-15393206 ] Gary Gregory commented on LOG4J2-1477: -- +1 > @NonNull support (for @NonNullByDefault or similar) >

[jira] [Commented] (LOG4J2-1476) New line is not appending in file logs

[ https://issues.apache.org/jira/browse/LOG4J2-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393180#comment-15393180 ] Harish HG commented on LOG4J2-1476: --- any suggestion?? > New line is not appending in file logs >

[jira] [Commented] (LOG4J2-1476) New line is not appending in file logs

[ https://issues.apache.org/jira/browse/LOG4J2-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393178#comment-15393178 ] Harish HG commented on LOG4J2-1476: --- This is the configuration of logs which I have used..

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393134#comment-15393134 ] Ralph Goers commented on LOG4J2-1477: - I would suggest this issue be deferred until the minimum

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

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

[jira] [Comment Edited] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392983#comment-15392983 ] yin mingjun edited comment on LOG4J2-1474 at 7/26/16 1:49 AM: -- OK, it's

[jira] [Commented] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392983#comment-15392983 ] yin mingjun commented on LOG4J2-1474: - OK, it's here! - break

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392887#comment-15392887 ] Remko Popma commented on LOG4J2-1465: - To address LOG4J2-1226 the most important next step is to

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392641#comment-15392641 ] Ralph Goers commented on LOG4J2-1465: - I agree with Gary. > Default layouts for various appenders

[jira] [Created] (LOG4J2-1480) CronTriggeringPolicy timing / file deletion issue

matthew beckham created LOG4J2-1480: --- Summary: CronTriggeringPolicy timing / file deletion issue Key: LOG4J2-1480 URL: https://issues.apache.org/jira/browse/LOG4J2-1480 Project: Log4j 2

[jira] [Commented] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392457#comment-15392457 ] Gary Gregory commented on LOG4J2-1341: -- How about a unit test that demonstrates the new code works

[jira] [Commented] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392436#comment-15392436 ] ASF GitHub Bot commented on LOG4J2-1341: Github user rzschech commented on the issue:

[jira] [Commented] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392437#comment-15392437 ] ASF GitHub Bot commented on LOG4J2-1341: GitHub user rzschech reopened a pull request:

[jira] [Commented] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392434#comment-15392434 ] ASF GitHub Bot commented on LOG4J2-1341: Github user rzschech commented on the issue:

[jira] [Commented] (LOG4J2-1341) (GC) Avoid allocating temporary objects in Pattern Converters for PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392429#comment-15392429 ] ASF GitHub Bot commented on LOG4J2-1341: Github user rzschech commented on the issue:

Jenkins build became unstable: Log4j 2.x #2103

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

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392289#comment-15392289 ] Matt Sicker commented on LOG4J2-1477: - You can configure IntelliJ to specify which annotation means

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392285#comment-15392285 ] Gary Gregory commented on LOG4J2-1465: -- Failing where it didn't before seems brutal unless we are

Re: Serializable Logger

Wouldn't it also be kind of an evil thing to do by adding Serializable to Logger mid-2.x? That kind of decision seems to be an x.0 type of decision. On 25 July 2016 at 11:55, Gary Gregory wrote: > Roger that. I suppose that we could make that part of an epic and note >

Re: Serializable Logger

Roger that. I suppose that we could make that part of an epic and note that Log4j's own implementations are fully supported (or not and which ones). I'm still not convinced that this is a "good thing" at the interface level because we could only document what each of our Logger implementations

[jira] [Created] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

Mikael Ståldal created LOG4J2-1479: -- Summary: Help Apache Spark project to upgrade from Log4j 1.x to 2.x Key: LOG4J2-1479 URL: https://issues.apache.org/jira/browse/LOG4J2-1479 Project: Log4j 2

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392260#comment-15392260 ] Mikael Ståldal commented on LOG4J2-1465: Since we would affect existing behaviour, I think it's

Re: Serializable Logger

The purpose is that the user of Log4j can be sure that the Logger is serializable. On Mon, Jul 25, 2016 at 6:38 PM, Gary Gregory wrote: > But to what purpose? Does Log4j itself need this? Is this a case of YAGNI? > > If I have a Logger in an object I serialize, and the

Re: Serializable Logger

But to what purpose? Does Log4j itself need this? Is this a case of YAGNI? If I have a Logger in an object I serialize, and the class implementing Logger is serializable, then I am good to go. Making Logger Serializable, would make this obvious to users and might make some developers warm and

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392236#comment-15392236 ] Mikael Ståldal commented on LOG4J2-1465: So what about changing default of those appenders which

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392204#comment-15392204 ] Ralph Goers commented on LOG4J2-1465: - IMO, changing default values should rarely be done as it will

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392194#comment-15392194 ] Mikael Ståldal commented on LOG4J2-1465: [~ralph_go...@dslextreme.com] do you think we can change

[jira] [Updated] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1465: --- Fix Version/s: 2.7 > Default layouts for various appenders could be more consistent >

[jira] [Commented] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392188#comment-15392188 ] Mikael Ståldal commented on LOG4J2-1465: Updated documentation to match current implementation.

[jira] [Assigned] (LOG4J2-1465) Default layouts for various appenders could be more consistent

[ https://issues.apache.org/jira/browse/LOG4J2-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1465: -- Assignee: Mikael Ståldal > Default layouts for various appenders could be more

Re: Serializable Logger

I think the theory is it is preferable to let implementors of an interface implement java.io.Serializable instead of letting the interface extend java.io.Serializable. That gives future implementors the freedom to choose to either implement Serializable or not. On Tue, Jul 26, 2016 at 12:49 AM,

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392153#comment-15392153 ] Greg Thomas commented on LOG4J2-1477: - Agreed; the best I've found seems to be

Re: Serializable Logger

It seems like serializable logger is useful in Apache Spark, which is popular to use from Scala. On Mon, Jul 25, 2016 at 4:20 PM, Matt Sicker wrote: > Do Scala programmers use Serializable a lot, or is there a better > mechanism there? Because if there's a more Scala way of

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392139#comment-15392139 ] Mikael Ståldal commented on LOG4J2-1477: I don't think we should use any Eclipse (or IntelliJ)

[jira] [Resolved] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1313. - Resolution: Fixed Fixed in master. The only change required was in PluginValueVisitor to use

[jira] [Assigned] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1313: --- Assignee: Remko Popma > not working > - > >

[jira] [Commented] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392022#comment-15392022 ] Matt Sicker commented on LOG4J2-1477: - I'm pretty sure IntelliJ has a feature to auto-add `@NonNull`

[jira] [Comment Edited] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392022#comment-15392022 ] Matt Sicker edited comment on LOG4J2-1477 at 7/25/16 2:45 PM: -- I'm pretty

Re: Apache Spark now more Log4j 2 friendly

Cool! On 25 July 2016 at 09:29, Gary Gregory wrote: > Nice! > > Gary > > On Jul 25, 2016 5:35 AM, "Ralph Goers" wrote: > >> Cool, Thanks! >> >> Ralph >> >> On Jul 25, 2016, at 1:08 AM, Mikael Ståldal >> wrote: >>

Re: Apache Spark now more Log4j 2 friendly

Nice! Gary On Jul 25, 2016 5:35 AM, "Ralph Goers" wrote: > Cool, Thanks! > > Ralph > > On Jul 25, 2016, at 1:08 AM, Mikael Ståldal > wrote: > > I have helped Apache Spark to be a bit more Log4j 2 friendly: > >

[jira] [Commented] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391994#comment-15391994 ] Matt Sicker commented on LOG4J2-1313: - You mean like a special case for attributes named "value"? >

Re: Serializable Logger

It feels like we need an epic to get our overall story straight on serialization, including docs on what works, doesn't, and what we plan to have working. Gary On Jul 25, 2016 1:06 AM, "Mikael Ståldal" wrote: > I am asking this since I'm considering making the Scala

Re: Serializable Logger

Do Scala programmers use Serializable a lot, or is there a better mechanism there? Because if there's a more Scala way of doing it, that would make more sense. Otherwise, you can always add Serializable later, but you shouldn't remove it once it's part of the public API. On 25 July 2016 at 03:06,

[jira] [Created] (LOG4J2-1478) SMTP appender which uses JNDI

Nicolò Chieffo created LOG4J2-1478: -- Summary: SMTP appender which uses JNDI Key: LOG4J2-1478 URL: https://issues.apache.org/jira/browse/LOG4J2-1478 Project: Log4j 2 Issue Type: Wish

[jira] [Updated] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

[ https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bojan Antonović updated LOG4J2-1477: Description: Eclipse (and other tools) offer non-null checks by annotation processing.

[jira] [Created] (LOG4J2-1477) @NonNull support (for @NonNullByDefault or similar)

Bojan Antonović created LOG4J2-1477: --- Summary: @NonNull support (for @NonNullByDefault or similar) Key: LOG4J2-1477 URL: https://issues.apache.org/jira/browse/LOG4J2-1477 Project: Log4j 2

[jira] [Updated] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1474: Description: I am migrating my project from log1.x to log2.x, and I was using

[jira] [Commented] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391925#comment-15391925 ] Remko Popma commented on LOG4J2-1474: - Is that the complete stack trace? Usually an

[jira] [Updated] (LOG4J2-1476) New line is not appending in file logs

[ https://issues.apache.org/jira/browse/LOG4J2-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish HG updated LOG4J2-1476: -- Description: New line is not appending in file logs, I used the pattern layout as below was:New

[jira] [Created] (LOG4J2-1476) New line is not appending in file logs

Harish HG created LOG4J2-1476: - Summary: New line is not appending in file logs Key: LOG4J2-1476 URL: https://issues.apache.org/jira/browse/LOG4J2-1476 Project: Log4j 2 Issue Type: Question

Re: Apache Spark now more Log4j 2 friendly

Cool, Thanks! Ralph > On Jul 25, 2016, at 1:08 AM, Mikael Ståldal wrote: > > I have helped Apache Spark to be a bit more Log4j 2 friendly: > > https://issues.apache.org/jira/browse/SPARK-16416 > > -- > > > Mikael Ståldal > Senior software developer > > Magine

[jira] [Updated] (LOG4J2-1475) High CPU utilization if large log message contains '${'

[ https://issues.apache.org/jira/browse/LOG4J2-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hikaru Abe updated LOG4J2-1475: --- Attachment: log4j2.xml dollar-braces.txt > High CPU utilization if large log message

[jira] [Commented] (LOG4J2-1475) High CPU utilization if large log message contains '${'

[ https://issues.apache.org/jira/browse/LOG4J2-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391740#comment-15391740 ] Hikaru Abe commented on LOG4J2-1475: if log message has many '${' token, the following code takes

[jira] [Created] (LOG4J2-1475) High CPU utilization if large log message contains '${'

Hikaru Abe created LOG4J2-1475: -- Summary: High CPU utilization if large log message contains '${' Key: LOG4J2-1475 URL: https://issues.apache.org/jira/browse/LOG4J2-1475 Project: Log4j 2 Issue

[jira] [Updated] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

[ https://issues.apache.org/jira/browse/LOG4J2-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yin mingjun updated LOG4J2-1474: Component/s: Core > CronTriggeringPolicy raise exception and fail to rollover log file when >

[jira] [Created] (LOG4J2-1474) CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true.

yin mingjun created LOG4J2-1474: --- Summary: CronTriggeringPolicy raise exception and fail to rollover log file when checkOnStartup is true. Key: LOG4J2-1474 URL: https://issues.apache.org/jira/browse/LOG4J2-1474

[jira] [Commented] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391594#comment-15391594 ] Remko Popma commented on LOG4J2-1313: - I think you are right about the empty string:

Apache Spark now more Log4j 2 friendly

I have helped Apache Spark to be a bit more Log4j 2 friendly: https://issues.apache.org/jira/browse/SPARK-16416 -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged

Re: Serializable Logger

I am asking this since I'm considering making the Scala Logger wrapper Serializable. Would that be a good idea? On Mon, Jul 25, 2016 at 10:00 AM, Mikael Ståldal wrote: > Users can rely on the fact that loggers are always Serializable. > > I guess we could also

Re: Serializable Logger

Users can rely on the fact that loggers are always Serializable. I guess we could also document that fact if we don't want to mark the interface Serializable. On Fri, Jul 22, 2016 at 7:16 PM, Ralph Goers wrote: > What advantage is gained by declaring the interface