![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0.13 |
|
Assignee:
|
Logback dev list
|
|
Attachments:
|
PrudentFileAppenderInterruptTest.java |
|
Components:
|
logback-core |
|
Created:
|
04/Jun/13 10:19 PM
|
|
Description:
|
If a thread is ever interrupted immediately followed by a logging call using a prudent FileAppender then the FileAppender is stopped and no logging can be done by any other thread.
FileLockInterruptedException is thrown by FileChannel.lock used in FileAppender.safeWrite. This exception should not stop the entire appender, for my use cases it would be enough to just catch the exception and reset the interrupted flag.
I've attached a very simple unit test that demonstrates this issue.
|
|
Environment:
|
N/A
|
|
Project:
|
logback
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Joe Jensen
|
|
|
|
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
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev
