[
https://issues.apache.org/jira/browse/LOG4J2-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039761#comment-14039761
]
Bobby commented on LOG4J2-662:
------------------------------
I had found the root cause, it seems like i carelessly didn't put log4j2.xml
into WEB-INF/classes folder, the classpath was set that way, but instead i put
it in WEB-INF folder, so it showed abnormal behaviour like the above.. I have
tested it and it worked fine :), including no deadlock issues like what
happened in log4j. This also conlude issue #661, if you confirm, i will close
the issue :D
Again, i apologize for this, but i sure do want to get rid of those
StatusLogger Error, although it is harmless as far as i tested it.
I didn't extract anything in WEB-INF/lib, just normal jar files reside there,
and yes, there is a dependency that still use log4j 1.2.
Thank you very much
> AsyncLogger Missing File Location and Line
> ------------------------------------------
>
> Key: LOG4J2-662
> URL: https://issues.apache.org/jira/browse/LOG4J2-662
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-rc1
> Environment: CentOS release 6.5 (Final)
> Memory 16GB
> AMD Phenom(tm) II X6 1090T Processor
> JBoss 7.1.0-cr1
> Reporter: Bobby
> Labels: async, file
> Attachments: log4j2-notshowing-file-location.png, log4j2-trace
> (2).png, log4j2.xml
>
>
> Using attached configuration file, i wasn't able to print filename and file
> line in log.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
