[jira] [Commented] (LOG4J2-1024) log4j2.xml not found by default in WEB-INF folder

[ https://issues.apache.org/jira/browse/LOG4J2-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562452#comment-14562452 ] Patrick Zimmermann commented on LOG4J2-1024: Adding a display name so

[jira] [Commented] (LOG4J2-1024) log4j2.xml not found by default in WEB-INF folder

[ https://issues.apache.org/jira/browse/LOG4J2-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561008#comment-14561008 ] Patrick Zimmermann commented on LOG4J2-1024: Following are the diffe

[jira] [Created] (LOG4J2-1024) log4j2.xml not found by default in WEB-INF folder

Patrick Zimmermann created LOG4J2-1024: -- Summary: log4j2.xml not found by default in WEB-INF folder Key: LOG4J2-1024 URL: https://issues.apache.org/jira/browse/LOG4J2-1024 Project: Log4j 2

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273181#comment-14273181 ] Patrick Flaherty commented on LOG4J2-908: - No trailing EOL, so it doesn&#

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272005#comment-14272005 ] Patrick Flaherty commented on LOG4J2-908: - If you check the gist output, I

[jira] [Commented] (LOG4J2-908) JSONLayout doesn't add a comma between log events

[ https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265357#comment-14265357 ] Patrick Flaherty commented on LOG4J2-908: - I sent an email to the log4j

AW: maven and jms

ooops, i'm sorry, as far as i can see, jms is not in that repository :-/ but others like javax.activation, javax.mail, javax.servlet etc. are in there. at least. > -Ursprüngliche Nachricht- > Von: Wyss Patrick [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 18. April 2

AW: maven and jms

alternatively you could add suns maven repository: https://maven-repository.dev.java.net/nonav/repository to the pom or settings: java.net https://maven-repository.dev.java.net/nonav/repository legacy however i do not see this often in OS projects, so i have no clue if this is considered

AW: "Compelling Reasons to adopt log4j2"

> > * Ease of migration/Drop in replacement for log4j 1.2 - If we do > > not meet this fundamental goal, I seriously doubt we'll ever gain > > traction. We should be free from the log4j1.2 design, but we > > should begin early to ensure that the core design can be easily > > shimmed with a

AW: log4j 1.3 PatternLayout repackaging and initial log4j 2.0 work

ed appenders as 'default' starting point: AppenderSkeleton and 'UnsychronizedAppenderSkeleton' (obviously i'm not nativ english speaker ;-) ) regards patrick wyss - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

AW: Google Summer of Code projects

get further information. best regards patrick > -Ursprüngliche Nachricht- > Von: Jacob Kjome [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 21. März 2007 05:47 > An: Log4J Developers List > Betreff: Re: Google Summer of Code projects > > > > I'm not su

AW: Re: Enhanced FileAppender

be done when creating a new file descriptor... i think a pool of configurable size is enough. starting new threads in log4j is IMO no good idea anyway... cheers patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

AW: Enhanced FileAppender

Files is kicking in. i would suggest that this happens in append() and not in a thread of its own. best regards patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Enhanced FileAppender

d be an idea to add a method public boolean closeFileAfter( LoggingEvent event ); to make it possible to close the files with a specific log event. but that's just some quick toughts ;-} best regards patrick Bender Heri wrote: > > Hello all > > Since in user list nobod

re: java.net.SocketException: Operation not supported (errno:223) from log4j

> I do not have knowledge on syslog appender. What it is? it's used to log to a remote syslog daemon. i'd recommend not having that appender if you do not need it :-] try running with only a console appender and then add the appenders you need ---

Re: java.net.SocketException: Operation not supported (errno:223) from log4j

on your machine? - can you manually open such a socket? - try running without the syslog appender. cheers patrick -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. August 2006 08:32 An: Log4J Developers List Betreff: Re: AW

AW: java.net.SocketException: Operation not supported (errno:223) from log4j

your app (which i seriously doubt) best regards patrick btw: please don't start a new thread on the maillist every working day... > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 28. August 2006 09:36 > An: log

Log4jRequestedFeature for FileAppender

hi, It's quite convenient to use Log4j for writing 'special' log messages into a 'Excel-like' file with the .xls extention . The pattern layout can contain tab delimited values in order to build a csv file, directly accessible via the http server with the proper mime-type information (i.e. ask