Bug 49349 - LoggingEvent stoped coming with AsyncAppender
Summary: LoggingEvent stoped coming with AsyncAppender
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: 1.2
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 03:34 UTC by PARAG GOYAL
Modified: 2010-05-27 03:46 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description PARAG GOYAL 2010-05-27 03:34:31 UTC 
In our application we are using Log4J 1.2.16 with AsyncAppender for better performance and get rid of blocking.

We have configured RollingFileAppender and SockedHubAppender with AsyncAppender 
in case of heavy log floods (around 5 logs per seconds) after 30 mins logging stopped.

After debugging we found that Buffer array list  is empty and Dispatcher thread is in blocking state.
Comment 1 PARAG GOYAL 2010-05-27 03:36:38 UTC 
sorry Dispatcher thread is WAITING state.
Comment 2 PARAG GOYAL 2010-05-27 03:46:19 UTC 
this situation is reached only when 100 sec at a time.