Dimitry Declercq created LOG4J2-416:
---
Summary: ConcurrentModificationException when logging maps that
are being worked on
Key: LOG4J2-416
URL: https://issues.apache.org/jira/browse/LOG4J2-416
Are you seeing log messages in your log file?
Sent from my iPhone
On 2013/10/03, at 18:21, Sudharma Puranik sudharma.pura...@gmail.com wrote:
Hello,
I have created a complete asyncLogger and have started my application, While
looking at the thread dump I See that the AsyncLogger is
[
https://issues.apache.org/jira/browse/LOG4J2-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784947#comment-13784947
]
Remko Popma commented on LOG4J2-416:
I'm not sure if it is possible to do this in a
[
https://issues.apache.org/jira/browse/LOG4J2-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13784947#comment-13784947
]
Remko Popma edited comment on LOG4J2-416 at 10/3/13 9:41 AM:
-
Yes I see log messages getting updated.
On Thu, Oct 3, 2013 at 2:54 PM, Remko Popma remko.po...@gmail.com wrote:
Are you seeing log messages in your log file?
Sent from my iPhone
On 2013/10/03, at 18:21, Sudharma Puranik sudharma.pura...@gmail.com
wrote:
Hello,
I have created a
If the events are being logged correctly I don't think there is a problem. The
async logger thread is either waiting for more work (log events) to arrive from
the ring buffer, or it has written to the disk and it is blocked (waiting) for
the I/O call to return.
Best regards,
Remko
Sent from
This is the dump log
AsyncLogger-1 daemon prio=6 tid=0x0dd3f800 nid=0x3444 runnable
[0x0f46f000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
at
Yes, waiting at that location means that the async logging thread is waiting
for new work to arrive. Assuming log events are appearing in the log file
correctly, I don't see any issue.
Best regards,
Remko
Sent from my iPhone
On 2013/10/03, at 19:28, Sudharma Puranik
ok, Thanks a lot for your quick reply, I actually wanted to have
asynchronous logging so I had previously done AsyncAppenders then I am
testing AsyncLoggers but frankly I am unable to understand the difference
between these. Can you please provide any blog of yours or any
explanination you have
You're welcome.
Christian's blog post has more details on the difference:
http://www.javacodegeeks.com/2013/07/log4j-2-performance-close-to-insane.html
Best regards,
Remko
Sent from my iPhone
On 2013/10/03, at 19:41, Sudharma Puranik sudharma.pura...@gmail.com wrote:
ok, Thanks a lot for
Oh wonderful, So it means to me that the difference is w.r.t the mechanism
used which makes the throughput better. So for AsyncLoggers , it uses
disruptor which has immense difference in performance compared to the
ArrayBlockingQueue.
But when I have multiple AsyncLoggers , that is mutiple
[
https://issues.apache.org/jira/browse/LOG4J2-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13785051#comment-13785051
]
Noel Grandin commented on LOG4J2-414:
-
Just a suggestion, but are we sure we know
Even if you configure multiple AsyncLoggers, there will be only one shared
ring buffer. For AsyncAppender, there will be one ArrayBlockingQueue +
Thread for every AsyncAppender configured.
The ring buffer used by AsyncLoggers is pre-allocated with
RingBufferLogEvent objects and with the default
[
https://issues.apache.org/jira/browse/LOG4J2-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13785231#comment-13785231
]
Remko Popma commented on LOG4J2-414:
Good point.
I've done some back-of-the-napkin
Thanks lot for the detailed explanation, I will definitely try this over
the weekend.
-Sudharma
On Thu, Oct 3, 2013 at 7:00 PM, Remko Popma remko.po...@gmail.com wrote:
Even if you configure multiple AsyncLoggers, there will be only one shared
ring buffer. For AsyncAppender, there will be
15 matches
Mail list logo
