[jira] [Commented] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156434#comment-16156434 ] Leonid Bogdanov commented on LOG4J2-2034: - BTW, a serialization exception is logged by Log4j

[jira] [Created] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

Leonid Bogdanov created LOG4J2-2035: --- Summary: There is no such lib as disruptor-3.3.3 Key: LOG4J2-2035 URL: https://issues.apache.org/jira/browse/LOG4J2-2035 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event in

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Attachment: log4j-issue.zip Demo project which reproduces the issue > In async mode

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event in

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Summary: In async mode JsonLayout can't serialize an event with self referenced throwable

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Affects Version/s: 2.8.2 > In async mode JsonLayout can't serialize an event with self

[jira] [Updated] (LOG4J2-2034) In async mode JsonLayout can't serialize an event with self referenced throwable

[ https://issues.apache.org/jira/browse/LOG4J2-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Bogdanov updated LOG4J2-2034: Description: When async logging is configured, JsonLayout cannot serialize a log event in

[jira] [Created] (LOG4J2-2034) in async mode JsonLayout can't serialize an event with self referenced throwable

Leonid Bogdanov created LOG4J2-2034: --- Summary: in async mode JsonLayout can't serialize an event with self referenced throwable Key: LOG4J2-2034 URL: https://issues.apache.org/jira/browse/LOG4J2-2034

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

I would expect all the dependencies to be marked as “provided” so it shouldn’t matter if they are all together. Ralph > On Sep 6, 2017, at 4:10 PM, Remko Popma wrote: > > I guess it depends on what dependencies this module requires. > > If this module requires Tomcat

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

I guess it depends on what dependencies this module requires. If this module requires Tomcat dependencies then perhaps log4j-tomcat is better because another container wouldn't want to drag in the Tomcat dependencies. If there's no dependency on any specific container or on any javaEE jars

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

The word container is so vague... container of what? Files, Applications, NoSQL things? How about app-container? Gary On Wed, Sep 6, 2017 at 4:07 PM, Remko Popma wrote: > log4j-container? > (To be more generic than javaee) > > > > On Sep 7, 2017, at 4:56, Ralph Goers

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

log4j-container? (To be more generic than javaee) > On Sep 7, 2017, at 4:56, Ralph Goers wrote: > > Yes, the intent would be to allow containers to use Log4j as their logging > implementation. > > Ralph > >> On Sep 6, 2017, at 12:26 PM, Mikael Ståldal

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

That was more or less my thought. In the main repo or a different one? Ralph > On Sep 6, 2017, at 3:07 PM, Remko Popma wrote: > > log4j-container? > (To be more generic than javaee) > > >> On Sep 7, 2017, at 4:56, Ralph Goers wrote: >> >>

Re: Log4j-audit

Yup, it is needed in log4j-catalog-jpa to get javax.persistence. I probably don’t need it in the other modules (except for the wars). Ralph > On Sep 6, 2017, at 1:13 PM, Mikael Ståldal wrote: > > I see that several modules depends on javax:javaee-api. Is that necessary? It

Re: Log4j-audit

I see that several modules depends on javax:javaee-api. Is that necessary? It should only be necessary in log4j-catalog-jpa, right? I see that log4j-catalog-api and log4j-catalog-git depends on javax:javaee-api and on Spring Framework. It would be better if those modules didn't. On

Re: Log4j-audit

Thanks, I will look at JavaPoet and see if it makes things any simpler. Only the web app and rest service depend on Spring. At this point it is a requirement. What JavaEE stuff? The catalog-war project is a user interface for editing the catalog. When I start creating documents I will take

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

Yes, the intent would be to allow containers to use Log4j as their logging implementation. Ralph > On Sep 6, 2017, at 12:26 PM, Mikael Ståldal wrote: > > Is the point to integrate with JavaEE containers, not necessarily from a web > app? > > Then I would suggest a new

Re: [Log4j] Broken link to ScalaDoc on site

Should that page even be in the manual any more? Ralph > On Sep 6, 2017, at 12:23 PM, Mikael Ståldal wrote: > > The ScalaDoc link on > https://logging.apache.org/log4j/2.x/manual/scala-api.html is broken. > >

Re: Log4j-audit

I had a quick look. Some comments: * You might want to use the JavaPoet library to generate Java source code, it is Apache-licensed, available on Maven central and has no transitive dependencies: https://github.com/square/javapoet * Some users might not like to depend on Spring Framework. *

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

Is the point to integrate with JavaEE containers, not necessarily from a web app? Then I would suggest a new module log4j-javaee, and to put it in the main repo. On 2017-09-06 20:49, Ralph Goers wrote: On the commons list I got some pointers on how to integrate with Tomcat 8.5+ and TomEE.

[Log4j] Broken link to ScalaDoc on site

The ScalaDoc link on https://logging.apache.org/log4j/2.x/manual/scala-api.html is broken.

[jira] [Commented] (LOG4J2-2033) Regression in ProviderUtil.hasProviders for 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155887#comment-16155887 ] Andre Burgoyne commented on LOG4J2-2033: I verified that the issue is resolved using the code

Log4j support for Tomcat, TomEE, JBoss, etc.

On the commons list I got some pointers on how to integrate with Tomcat 8.5+ and TomEE. I’ve written the class that is required but am wondering where to put it. It could go in log4j-core, but that isn’t where we have been putting these things. It really shouldn’t go in log4j-web as users may

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155529#comment-16155529 ] member sound commented on LOG4J2-1259: -- I can confirm adding log4j-web*.jar to jarsToSkip fixes the

[jira] [Updated] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2031: - Fix Version/s: (was: 2.9.1) > Log4j2 log file not reflecting application log function calls

Re: Moving log4net-logviewer to apache

> On 6 Sep 2017, at 15:03, Dominik Psenner wrote: > > > On 2017-09-06 14:17, Oskar Gewalli wrote: >> Hi, >> >> Perhaps it would be better to create a dedicated library to just the log4net >> xml parsing? The GUI and CLI tools could then depend on that package. >> >>

Re: Moving log4net-logviewer to apache

On 2017-09-06 14:17, Oskar Gewalli wrote: Hi, Perhaps it would be better to create a dedicated library to just the log4net xml parsing? The GUI and CLI tools could then depend on that package. Since the log parsing parts are much smaller and not very special. I don't have the insights to

Re: Moving log4net-logviewer to apache

Hi, Perhaps it would be better to create a dedicated library to just the log4net xml parsing? The GUI and CLI tools could then depend on that package. Since the log parsing parts are much smaller and not very special. Best regards from Oskar > On 6 Sep 2017, at 13:54, Dominik Psenner

Re: Moving log4net-logviewer to apache

Hi Oskar, log4net-logviewer is a tool that includes both a command line and a ui frontend written in wpf/xaml that both can parse logfiles and provide users a better view on log events. According to the readme this is a alternative to log2console and chainsaw. I don't like it to have

[jira] [Commented] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs

[ https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155202#comment-16155202 ] Gabriel Klappenbach commented on LOG4J2-1769: - I don't see 2.7.1 in maven central repository,

[jira] [Commented] (LOG4J2-2031) Log4j2 log file not reflecting application log function calls

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154970#comment-16154970 ] Colin McDowell commented on LOG4J2-2031: Appreciate you taking time to look at the issue Remko.