The error message regarding the recursive call indicates that an appender is
logging an event which is being routed to the same appender. Log4j detects
that and ignores the logging event. But without seeing a stack trace it would
be impossible to guess what is going on. I can’t even tell what
I only have log4j-slf4j-impl
org.apache.logging.log4j
log4j-api
${log4j.version}
org.apache.logging.log4j
log4j-core
${log4j.version}
org.apache.logging.log4j
Did this resolve the problem?
On Friday, 11 December 2015, Remko Popma wrote:
> You may have both the log4j-to-slf4j adapter jar and the log4j-slf4j-impl
> jar on the classpath. They will route calls to each other. You need to
> remove one of them.
>
> Sent from my iPhone
>
> > On 2015/12/11, at
You may have both the log4j-to-slf4j adapter jar and the log4j-slf4j-impl jar
on the classpath. They will route calls to each other. You need to remove one
of them.
Sent from my iPhone
> On 2015/12/11, at 10:55, Priya Ahuja wrote:
>
> Hi,
>
> Any idea why I am seeing stackoverflow error? I
Hi,
Any idea why I am seeing stackoverflow error? I am using log4j2 and LOGFILE
is my rolling file appender.
Exception in thread
"pool-28-thread-2-workitem-HOST-cf95a544-c4b1-4084-861b-80e4ed4f4045-workitem-HOST-56de5b12-2d80-49c8-8b21-90433c89a2a1"
java.lang.StackOverflowError
Exception in threa
