Remko,
I just noticed that the log4j-async project is creating log files in the root
directory of the project. This is bad practice. Can you modify the tests so
that all the log files are written under the target directory?
Ralph
+1. Yes, the ability for log4j 2 to provide native JMX support would be
fantastic. There are only custom solutions for this with log4j 1.
On Tue, Apr 2, 2013 at 7:35 PM, Ralph Goers wrote:
> Features I would like to see in JMX:
> 1. Show all the LoggerContexts and their configurations.
> 2. Abi
[
https://issues.apache.org/jira/browse/LOG4J2-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-194:
---
Description:
Failed tests:
testSeparatorAsDefaultLineSeparator(org.apache.logging.log4j.core.impl.
Remko Popma created LOG4J2-194:
--
Summary: broken JUnit test ThrowableFormatOptionsTest (breaks the
build)
Key: LOG4J2-194
URL: https://issues.apache.org/jira/browse/LOG4J2-194
Project: Log4j 2
Features I would like to see in JMX:
1. Show all the LoggerContexts and their configurations.
2. Ability to modify a configuration (this should involve cloning the current
configuration, modifying it and then replacing the prior configuration with the
new one).
3. Statistics from various compone
date-images-20130402.patch and
documentation-update-20130402.patch.
I proposed a patch for LOG4J2-193 which has the same documentation changes.
Sorry for the confusion.
> Create asynchronous Logger for low-latency
[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-163.
--
> Create asynchronous Logger for low-latency logging
>
[
https://issues.apache.org/jira/browse/LOG4J2-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-193:
---
Attachment: LOG4J2-193-with-doc-updates.patch
documentation-update-images-20130402
[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-163:
---
Attachment: (was: documentation-update-20130402.patch)
> Create asynchronous Logger for
[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-163:
---
Attachment: (was: documentation-update-images-20130402.patch)
> Create asynchronous Log
Remko Popma created LOG4J2-193:
--
Summary: RollingFastFileAppender (in log4j-async) does not roll
over
Key: LOG4J2-193
URL: https://issues.apache.org/jira/browse/LOG4J2-193
Project: Log4j 2
Issu
Tom Hegermann created LOG4J2-192:
Summary: ${env:...} is not replaced in fileName
Key: LOG4J2-192
URL: https://issues.apache.org/jira/browse/LOG4J2-192
Project: Log4j 2
Issue Type: Bug
Af
https://issues.apache.org/bugzilla/show_bug.cgi?id=49693
Fabrice changed:
What|Removed |Added
Target Milestone|--- |1.2.18
--- Comment #3 from Fabrice ---
https://issues.apache.org/bugzilla/show_bug.cgi?id=49693
--- Comment #2 from Fabrice ---
Hi,
I came accross this issue while researching a similar behavior on our systems.
When rolling at midnight (using companions, we create a folder based on date)
we intermittently lose the logs.
Bascially t
I would like to take a stab at implementing JMX support for log4j2.
What features would you like to see with regards to JMX? Ideas are welcome!
15 matches
Mail list logo
