[
https://issues.apache.org/jira/browse/LOG4J2-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-469.
Resolution: Fixed
Fix Version/s: 2.0-rc2
Fix for FailoverAppender applied in revision
See
http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/tutorial/doc/SJSXP2.html
for STAX vs DOM. Note that Log4j configurations are typically fairly small.
Unless some problem arises with using DOM I see no reason to change anything.
Ralph
On May 11, 2014, at 9:27 PM, Matt
[
https://issues.apache.org/jira/browse/LOG4J2-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994848#comment-13994848
]
Ralph Goers commented on LOG4J2-469:
The JDBC connection issue was resolved in
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995060#comment-13995060
]
Mikael Ståldal commented on LOG4J2-623:
---
The syntax of the generated JSON is
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-623:
--
Comment: was deleted
(was: The syntax of the generated JSON is invalid, it looks like this:
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal reopened LOG4J2-623:
---
The syntax of the generated JSON is invalid, it looks like this:
{code:xml}
{
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995105#comment-13995105
]
Gary Gregory commented on LOG4J2-623:
-
I am putting the finishing touches on redoing
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-623.
Resolution: Fixed
Fix Version/s: 2.0-rc2
I have removed the incorrect trailing '} in
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995116#comment-13995116
]
Ralph Goers commented on LOG4J2-623:
Gary, the correct syntax for a map in JSON is
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995115#comment-13995115
]
Mikael Ståldal commented on LOG4J2-623:
---
Can you give a concrete example of what the
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal closed LOG4J2-623.
-
Now I get this:
{code}
{
logger:MyLogger,
timestamp:1399907141921,
level:INFO,
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995168#comment-13995168
]
Gary Gregory commented on LOG4J2-623:
-
You should expect the following before 2.0
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995192#comment-13995192
]
Ralph Goers commented on LOG4J2-623:
Unless you can provide a reason that the
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995287#comment-13995287
]
Ralph Goers commented on LOG4J2-623:
That is hardly surprising since the JSON spec
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995225#comment-13995225
]
Gary Gregory commented on LOG4J2-623:
-
Simple: If it is not this way, it is *not*
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-461:
---
Component/s: (was: API)
log4j 1.2 emulation
ERROR StatusLogger Unable to
I would certainly say that in like 99% of cases (probably more),
ThreadLocal variables are meant to be static (otherwise I'd tend to use a
different data structure like AtomicReference). Anyway, the documentation
makes this a little strange, but I can't see a reason to use a ThreadLocal
instance
This could be more useful for consuming log events possibly. For
configuration, DOM works fine it seems.
On 12 May 2014 01:36, Ralph Goers ralph.go...@dslextreme.com wrote:
See
http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/tutorial/doc/SJSXP2.html
for
STAX vs DOM.
My bad on this one. Thank you Remko.
Gary
-- Forwarded message --
From: rpo...@apache.org
Date: Mon, May 12, 2014 at 9:21 PM
Subject: svn commit: r1594112 -
/logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/AbstractLogEvent.java
To:
No problem at all.
:-)
On Tue, May 13, 2014 at 10:24 AM, Gary Gregory garydgreg...@gmail.comwrote:
My bad on this one. Thank you Remko.
Gary
-- Forwarded message --
From: rpo...@apache.org
Date: Mon, May 12, 2014 at 9:21 PM
Subject: svn commit: r1594112 -
[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995487#comment-13995487
]
Gary Gregory commented on LOG4J2-623:
-
As a reminder, the goal is to be able to ship a
Good question. In the current usage, the ThreadContext class has a static
reference to a DefaultThreadContextMap.
So essentially DefaultThreadContextMap is a singleton and the localMap
ThreadLocal could be either static or non-static, it doesn't matter.
Perhaps we can rephrase the question as:
Is
I prefer to move all classes into the helpers directory and get rid of lang.
Why ResourceLoaders deserve to be placed in a “lang” package doesn’t make a lot
of sense to me - they could just as easily have been placed into a package
called util. I just didn’t notice when the lang subproject
Gary Gregory created LOG4J2-634:
---
Summary: ThrowableProxy ctor throws an exception when using
suppressed exceptions
Key: LOG4J2-634
URL: https://issues.apache.org/jira/browse/LOG4J2-634
Project: Log4j
24 matches
Mail list logo
