[jira] [Commented] (LOG4J2-1482) Improper header in CsvParameterLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395101#comment-15395101 ] Sumit Singhal commented on LOG4J2-1482: --- I've attached the sample output files also. Here,

[jira] [Commented] (LOG4J2-1482) Improper header in CsvParameterLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395083#comment-15395083 ] Gary Gregory commented on LOG4J2-1482: -- Can you provide an example please? I want to make sure I

[jira] [Created] (LOG4J2-1482) Improper header in CsvParameterLayout

Sumit Singhal created LOG4J2-1482: - Summary: Improper header in CsvParameterLayout Key: LOG4J2-1482 URL: https://issues.apache.org/jira/browse/LOG4J2-1482 Project: Log4j 2 Issue Type: Bug

Re: Build failed in Jenkins: Log4j 2.x #2106

That's a strange one. Maybe an experimental build slave again? On 26 July 2016 at 19:41, Apache Jenkins Server wrote: > See > > Changes: > > [ggregory] [LOG4J2-1467][OSGi] Missing import package.

Build failed in Jenkins: Log4j 2.x #2106

See Changes: [ggregory] [LOG4J2-1467][OSGi] Missing import package. [LOG4J2-351][OSGi] wrong [ggregory] Add missing '@Override' annotations. [ggregory] Remove unused imports. -- Started by an SCM

[jira] [Commented] (LOG4J2-1467) [OSGi] Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394840#comment-15394840 ] Gary Gregory commented on LOG4J2-1467: -- Good point, testing with Eclipse Equinox and Apache Felix

[jira] [Resolved] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

[ https://issues.apache.org/jira/browse/LOG4J2-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-351. - Resolution: Fixed Fix Version/s: 2.7 Please verify and close (assuming you can build

[jira] [Resolved] (LOG4J2-1467) [OSGi] Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1467. -- Resolution: Fixed Fix Version/s: 2.7 Please verify and close (assuming you can build

[jira] [Updated] (LOG4J2-1467) [OSGi] Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1467: - Summary: [OSGi] Missing import package (was: OSGi: Missing import package) > [OSGi] Missing

[jira] [Reopened] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

[ https://issues.apache.org/jira/browse/LOG4J2-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-351: - Re-opening, the {{Fragment-Host}} manifest entry is gone. > [OSGi] wrong Fragment-Host in manifest

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

My “opinion" is that it should be possible to create a Configuration implementation from any of these. Ralph > On Jul 26, 2016, at 1:43 PM, Gary Gregory wrote: > > No, no. What I am saying overall is that it would be nice for Log4j to at > least have a documented

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

No, no. What I am saying overall is that it would be nice for Log4j to at least have a documented opinion on JDNI, j.u.prefs, and anything else like Commons Configuration. Gary On Tue, Jul 26, 2016 at 12:58 PM, Ralph Goers wrote: > The configuration for JDBC is

[jira] [Comment Edited] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394474#comment-15394474 ] Gary Gregory edited comment on LOG4J2-1467 at 7/26/16 8:33 PM: --- I think

[jira] [Comment Edited] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394491#comment-15394491 ] Gary Gregory edited comment on LOG4J2-1467 at 7/26/16 8:30 PM: --- Hm... right

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394491#comment-15394491 ] Gary Gregory commented on LOG4J2-1467: -- Hm... right now log4j-api and log4j-core both have Bundle

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394486#comment-15394486 ] Gary Gregory commented on LOG4J2-1467: -- >From

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394479#comment-15394479 ] Matt Sicker commented on LOG4J2-1467: - That Fragment-Host manifest header isn't in the pom anymore.

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394474#comment-15394474 ] Gary Gregory commented on LOG4J2-1467: -- I think that what [~rakus] is saying is that any Log4j

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

The configuration for JDBC is typically a single string. You aren’t really thinking of storing log4j2.xml as a single String in JNDI are you? Key/Value pairs is what java.util.prefs does. Ralph > On Jul 26, 2016, at 11:34 AM, Gary Gregory wrote: > > I've used JDNI to

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394355#comment-15394355 ] Matt Sicker commented on LOG4J2-1467: - >From what I remember, each bundle's BundleContext is used to

[jira] [Commented] (LOG4J2-1481) Wrong logger's name in patterns with long output

[ https://issues.apache.org/jira/browse/LOG4J2-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394333#comment-15394333 ] Roman Koretskiy commented on LOG4J2-1481: - for current pattern expected to see first two level of

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

JNDI is handy in OSGi, but it's a secondary way of accessing registered services (there are much easier ways to get said service references than via JNDI). On 26 July 2016 at 13:34, Gary Gregory wrote: > I've used JDNI to deal with configuring JDBC connections in app

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

I've used JDNI to deal with configuring JDBC connections in app servers. It seems to work. I've not had the same painful experience as you've had. Granted, a JDBC DataSource object is not as fancy as our configuration. The big advantage JDBC has WRT configuration is that you usually can configure

[jira] [Commented] (LOG4J2-1467) OSGi: Missing import package

[ https://issues.apache.org/jira/browse/LOG4J2-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394231#comment-15394231 ] Ralf commented on LOG4J2-1467: -- Regarding the point "... but has no idea which classloader should be used."

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

I dislike java.util.prefs almost as much as JNDI, but I am actually surprised you didn’t mention that. I did try to use java.util.prefs once. I ended up using Commons Configuration instead (which is also something else we could potentially integrate with). Ralph > On Jul 26, 2016, at 10:33

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

Has anybody asked for that? To be honest, the JNDI API is one of the worst designs ever. It is impossible not to get an exception during normal operation. If I was going to implement “advanced” configuration I would be looking at zookeeper or something similar. Ralph > On Jul 26, 2016, at

Re: JAX innovation awards 2016

Remko: Did you submit as well? G On Tue, Jul 26, 2016 at 9:58 AM, Remko Popma wrote: > Nice! Now we need to get lots of votes in! :-) > > On Wed, Jul 27, 2016 at 12:49 AM, Gary Gregory > wrote: > >> Me too :-) >> >> Gary >> >> On Tue, Jul 26,

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

To load different bits of configuration. Or the whole thing. The question is: How should JNDI be used to configure Log4j. It could be the whole config and our config lookup could be made to use JNDI or it could be bits and pieces of different components like this last request. Gary On Tue, Jul

Re: JAX innovation awards 2016

Nice! Now we need to get lots of votes in! :-) On Wed, Jul 27, 2016 at 12:49 AM, Gary Gregory wrote: > Me too :-) > > Gary > > On Tue, Jul 26, 2016 at 7:47 AM, Matt Sicker wrote: > >> Cool! I nominated Log4j 2. >> >> On 26 July 2016 at 04:53, Remko

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394071#comment-15394071 ] Remko Popma commented on LOG4J2-1010: - This is now available in branch {{LOG4J2-1010}}. Please

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394062#comment-15394062 ] Remko Popma commented on LOG4J2-1447: - This is now available in branch {{LOG4J2-1010}}. Please

Re: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

To do what? I’ve never really used JNDI for much (except when I actually wanted to access LDAP). Ralph > On Jul 26, 2016, at 8:49 AM, Gary Gregory wrote: > > Any thoughts on a JNDI configuration epic? > > Gary > > -- Forwarded message -- > From:

Fwd: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI

Any thoughts on a JNDI configuration epic? Gary -- Forwarded message -- From: Nicolò Chieffo (JIRA) Date: Tue, Jul 26, 2016 at 4:59 AM Subject: [jira] [Updated] (LOG4J2-1478) SMTP appender which uses JNDI To: garydgreg...@gmail.com [

Re: JAX innovation awards 2016

Me too :-) Gary On Tue, Jul 26, 2016 at 7:47 AM, Matt Sicker wrote: > Cool! I nominated Log4j 2. > > On 26 July 2016 at 04:53, Remko Popma wrote: > >> Log4j 2 totally qualifies for this >> http://ow.ly/yAxG302yQJf >> >> Sent from my iPhone >> > > > >

[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=15393943#comment-15393943 ] Ralph Goers commented on LOG4J2-1477: - Yeah, I got confused by

Re: JAX innovation awards 2016

Cool! I nominated Log4j 2. On 26 July 2016 at 04:53, Remko Popma wrote: > Log4j 2 totally qualifies for this > http://ow.ly/yAxG302yQJf > > Sent from my iPhone > -- Matt Sicker

Re: Serializable Logger

Ah, thank you. On Tue, Jul 26, 2016 at 10:33 PM, Mikael Ståldal wrote: > The use case is here: https://issues.apache.org/jira/browse/LOG4J2-801 > > On Tue, Jul 26, 2016 at 2:43 PM, Remko Popma > wrote: > >> What is the exact use case? Who needs

[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=15393861#comment-15393861 ] Matt Sicker commented on LOG4J2-1477: - I don't see any NonNull annotation in the JDK, either. There's

Re: Serializable Logger

The use case is here: https://issues.apache.org/jira/browse/LOG4J2-801 On Tue, Jul 26, 2016 at 2:43 PM, Remko Popma wrote: > What is the exact use case? Who needs this, and what do they want to > accomplish? > If Apache Spark needs this we should be able to find out more

Re: Serializable Logger

What is the exact use case? Who needs this, and what do they want to accomplish? If Apache Spark needs this we should be able to find out more without having to guess... On Tue, Jul 26, 2016 at 9:36 PM, Mikael Ståldal wrote: > And if we cannot fix it, we should remove

Re: Serializable Logger

And if we cannot fix it, we should remove Serializable from AbstractLogger. On Tue, Jul 26, 2016 at 2:06 PM, Mikael Ståldal wrote: > If that's the case, we should reopen > https://issues.apache.org/jira/browse/LOG4J2-801 > > > On Tue, Jul 26, 2016 at 1:47 PM, Remko

Re: Serializable Logger

If that's the case, we should reopen https://issues.apache.org/jira/browse/LOG4J2-801 On Tue, Jul 26, 2016 at 1:47 PM, Remko Popma wrote: > But realistically it may not be easy to spin up a background thread etc on > deserialization. > > Sent from my iPhone > > On

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

[ https://issues.apache.org/jira/browse/LOG4J2-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolò Chieffo updated LOG4J2-1478: --- Attachment: JndiSmtpManager262.java JndiSmtpAppender262.java I don't know if

Re: Serializable Logger

That deserialized loggers work (given that all needed dependencies are on classpath) is a reasonable expectation. If we cannot guarantee that, then we should not declare that loggers are serializable. On Tue, Jul 26, 2016 at 11:45 AM, Remko Popma wrote: > Sure. What is

JAX innovation awards 2016

Log4j 2 totally qualifies for this http://ow.ly/yAxG302yQJf Sent from my iPhone

[jira] [Commented] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

[ https://issues.apache.org/jira/browse/LOG4J2-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393504#comment-15393504 ] VijayaKumar Guddeti commented on LOG4J2-1250: - sharing few more finding from the testing done

[jira] [Updated] (LOG4J2-1473) Inform other Apache projects using Log4j 1.x that it won't be supported in JDK9

[ https://issues.apache.org/jira/browse/LOG4J2-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1473: --- Description: Due to various issues in Log4j 1.2.x, it will no longer work in JDK9:

[jira] [Updated] (LOG4J2-1473) Inform other Apache projects using Log4j 1.x that it won't be supported in JDK9

[ https://issues.apache.org/jira/browse/LOG4J2-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1473: --- Description: Due to various issues in Log4j 1.2.x, it will no longer work in JDK9.

Re: Serializable Logger

Can we at least document that we guarantee that Loggers from log4j-impl are always serializable? On Tue, Jul 26, 2016 at 1:52 AM, Remko Popma wrote: > > On 2016/07/26, at 1:43, Mikael Ståldal wrote: > > The purpose is that the user of Log4j can

[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=15393396#comment-15393396 ] Greg Thomas commented on LOG4J2-1477: - AFAICT, there is no @NonNull in the JDK; you still need to

[jira] [Resolved] (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 resolved LOG4J2-1465. Resolution: Won't Fix > Default layouts for various appenders could be more consistent >

Re: Serializable Logger

Apache Spark needs serializable loggers, and if we can guarantee that Log4j 2 is then that would be a good argument to convince Spark users to use Log4j 2. http://stackoverflow.com/questions/29208844/apache-spark-logging-within-scala On Tue, Jul 26, 2016 at 1:52 AM, Remko Popma

[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=15393325#comment-15393325 ] Remko Popma edited comment on LOG4J2-1476 at 7/26/16 7:37 AM: -- Issue

[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=15393325#comment-15393325 ] Harish HG commented on LOG4J2-1476: --- Issue solved..Thanks for the reply @Remko Popma, I used the

[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 ] Harish HG edited comment on LOG4J2-1476 at 7/26/16 6:38 AM: This is the

[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=15393316#comment-15393316 ] Harish HG commented on LOG4J2-1476: --- It's working fine in window(new line in file logs) but in linux

[jira] [Created] (LOG4J2-1481) Wrong logger's name in patterns with long output

Roman Koretskiy created LOG4J2-1481: --- Summary: Wrong logger's name in patterns with long output Key: LOG4J2-1481 URL: https://issues.apache.org/jira/browse/LOG4J2-1481 Project: Log4j 2