JBoss EAP 5 stalls Threads blocking in AsyncHandler.
Issue
- Why HTTP Threads Waiting/Blocked to gain lock on logger on EAP 5?
- What is Async Appender Buffer Size in EAP 5?
- How to discard new log events in case of Buffer is full when using AsyncAppender in EAP 5?
- Following is the stack trace of one of thread blocked on Async Handler.
"http-x.x.x.x-8080-y" daemon prio=10 tid=0x00002aaac4229800 nid=0x5746 waiting for monitor entry [0x0000000059b1a000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:204)
- waiting to lock <0x0000000682e73110> (a org.apache.log4j.spi.RootLogger)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.log(Category.java:856)
at sun.reflect.GeneratedMethodAccessor292.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.logging.impl.Log4jProxy.log(Log4jProxy.java:311)
at org.apache.commons.logging.impl.Log4jProxy.debug(Log4jProxy.java:263)
at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:128)
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5.x.x
- Log4j
- 1.2.14.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.