https://issues.apache.org/bugzilla/show_bug.cgi?id=55481
Bug ID: 55481
Summary: Log4J Configuration in Virgo Jetty Server
Product: Log4j
Version: unspecified
Hardware: PC
OS: Windows Vista
Status: NEW
I took a look. Still a bit rough, but people have started to integrate the
disruptor into Logback.
Unfortunately cp149 did not mention the software versions used, what OS
they ran the performance test on, or any detail on the hardware they used
(number of cores would be nice to know...), so it is
wei wang created LOG4J2-369:
---
Summary: How to include the log4j2 lib jar into a jar with my
application class and run it ?
Key: LOG4J2-369
URL: https://issues.apache.org/jira/browse/LOG4J2-369
Project:
Roland Weiglhofer created LOG4J2-370:
Summary: Log4j2 OSGi How-To
Key: LOG4J2-370
URL: https://issues.apache.org/jira/browse/LOG4J2-370
Project: Log4j 2
Issue Type: Documentation
Also, does the version of the disruptor jar matter? I see that we are not
on the latest version 3.2.0 for trunk.
Gary
On Mon, Aug 26, 2013 at 6:47 AM, Remko Popma remko.po...@gmail.com wrote:
I took a look. Still a bit rough, but people have started to integrate the
disruptor into Logback.
[
https://issues.apache.org/jira/browse/LOG4J2-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750118#comment-13750118
]
Gary Gregory commented on LOG4J2-333:
-
Hervé,
I committed the changes. Please verify
Gus Heck created LOG4J2-371:
---
Summary: mvn test won't build
Key: LOG4J2-371
URL: https://issues.apache.org/jira/browse/LOG4J2-371
Project: Log4j 2
Issue Type: Bug
Components: Core
[
https://issues.apache.org/jira/browse/LOG4J2-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-371.
-
Resolution: Fixed
Fix Version/s: 2.0-beta9
Assignee: Gary Gregory
This is
[
https://issues.apache.org/jira/browse/LOG4J2-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reopened LOG4J2-364:
-
The doc changes (lookups.xml) breaks PDF generation.
WebLookup
-
[
https://issues.apache.org/jira/browse/LOG4J2-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750118#comment-13750118
]
Gary Gregory edited comment on LOG4J2-333 at 8/26/13 2:53 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-333.
-
Resolution: Fixed
Fix Version/s: 2.0-beta9
Assignee: Gary Gregory
Match
[
https://issues.apache.org/jira/browse/LOG4J2-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750124#comment-13750124
]
Gary Gregory edited comment on LOG4J2-364 at 8/26/13 2:53 PM:
--
I just re-arranged and analyzed the results posted in
https://github.com/cp149/jactor-logger. I did not actually rerun the perf
tests. (That is on the todo list but quite a bit of work...)
Is this officially part of Logback? (Seemed a bit rough and
work-in-progressy to me...)
On Mon, Aug 26,
Gary, yes versions matter. For cp149's stuff, I don't know what version of
Log4j2 they used, what version of Logback and what version of the
disruptor...
We should probably upgrade to 3.2 for trunk, btw, thanks for the reminder!
On Mon, Aug 26, 2013 at 11:20 PM, Gary Gregory
Am 26.08.13 16:55, schrieb Remko Popma:
I just re-arranged and analyzed the results posted
in https://github.com/cp149/jactor-logger. I did not actually rerun
the perf tests. (That is on the todo list but quite a bit of work...)
Is this officially part of Logback? (Seemed a bit rough and
[
https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reopened LOG4J2-307:
re-open to update version number
Upgrade LMAX disruptor library from 3.0.1 to 3.1.1
[
https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-307.
Resolution: Fixed
Updated to disruptor 3.2.0 in revision 1517552.
Upgrade LMAX
[
https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-307:
---
Description:
Upgrade LMAX Disruptor library from 3.0.1 to 3.1.1.
Edit 2013-8-26: the latest version
Roland Weiglhofer created LOG4J2-372:
Summary: Build-path-issue. Invalid file or path...
Key: LOG4J2-372
URL: https://issues.apache.org/jira/browse/LOG4J2-372
Project: Log4j 2
Issue
[
https://issues.apache.org/jira/browse/LOG4J2-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750166#comment-13750166
]
Remko Popma edited comment on LOG4J2-372 at 8/26/13 3:57 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750274#comment-13750274
]
Ralph Goers commented on LOG4J2-368:
The 1.2 bridge is meant to be the minimum amount
[
https://issues.apache.org/jira/browse/LOG4J2-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-364.
Resolution: Fixed
PDF generation was fixed in revision 1517619.
WebLookup
[
https://issues.apache.org/jira/browse/LOG4J2-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750359#comment-13750359
]
Ralph Goers commented on LOG4J2-372:
mvn eclipse:eclipse works fine on my Mac. I'll
[
https://issues.apache.org/jira/browse/LOG4J2-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-368.
Resolution: Fixed
Fix Version/s: 2.0-beta9
Assignee: Ralph Goers
Fixed in revision
Hi,
For every new category created a new entry is added into
org.apache.log4j.Hierarchy.ht. And at the same time also for any
possible parent category of that new entry.
This cache is fine when you have a fairly fixed number possible
categories. That cache will grow to some size and
[
https://issues.apache.org/jira/browse/LOG4J2-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750534#comment-13750534
]
Gus Heck commented on LOG4J2-368:
-
It allows velocity to render my template.
[
https://issues.apache.org/jira/browse/LOG4J2-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gus Heck closed LOG4J2-368.
---
PatternLayout in 1.2 bridge missing constructor
---
First, you are referring to Log4j 1.x. Most of our work is currently focused
on Log4j 2. That said, you would have the same issue with Log4j 2, Logback or
even java.util.logging.
What possible reason could you have for creating a logger per subscriber? The
key to us being able to provide
28 matches
Mail list logo
