![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0.13 |
|
Assignee:
|
Logback dev list
|
|
Attachments:
|
Screen Shot 2013-05-26 at 6.12.03 PM.png |
|
Components:
|
logback-classic |
|
Created:
|
26/May/13 1:18 PM
|
|
Description:
|
If application have multiple classloader ,like Websphere.
There is a chance that one classloader which load LoggerConext and another load logback.xml. This incident lead to "can NOT find [logback.xml]" message.
Reproduce problem :
1.Using spring scheduler which is launched before web sevlets start-> this will produce 2 classloader in single application.
2. Using shared library which have slf4j & logback jar file.
after launch , the first classloader is set classpath to shared library . The second one is load class from web's WEB-INF/class which have logback.xml
After using StatusPrinter.print(lc);
logback will print "can NOT find [logback.xml]".
interim solution for me:
solution 1: copy logback.xml into shared library
solution 2: change classloader behaviour to single classloader per application.
Attached file for more info.
|
|
Environment:
|
Websphere 6.1
|
|
Project:
|
logback
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
ThisadeeP
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
