[logback-dev] [JIRA] (LOGBACK-1406) Seems all threads blocked
Title: Message Title Ralph Goers commented on LOGBACK-1406 Re: Seems all threads blocked Let me see if I understand. You would like to have tryLock used instead and if the lock cannot be obtained then the log event would be discarded? Add Comment This message was sent by Atlassian JIRA (v7.3.1#73012-sha1:68837e3) ___ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev
[logback-dev] [JIRA] (LOGBACK-1481) When encoder pattern set as a variable then logback skips newline %n
Sergey Ponomarev created LOGBACK-1481:
-
Summary: When encoder pattern set as a variable then logback skips
newline %n
Key: LOGBACK-1481
URL: https://jira.qos.ch/browse/LOGBACK-1481
Project: logback
Issue Type: Bug
Components: logback-core
Affects Versions: 1.2.3
Environment: Linux
Reporter: Sergey Ponomarev
Assignee: Logback dev list
Priority: Minor
I have following logback.xml:
{code}
${pattern}
{code}
Then all log statements are written in the single line even given than the
pattern have %n in the end
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
___
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev
[logback-dev] [JIRA] (LOGBACK-1406) Seems all threads blocked
Title: Message Title Ala Schneider commented on LOGBACK-1406 Re: Seems all threads blocked OutputStreamAppender.java method writeBytes makes infinite lock of ReentrantLock lock. This is the reason of stagnation. Only process restart may help. At least this is the problem of logback-core version 1.2.3. Using of tryLock with some reasonable timeout is better - the current message will be lost, but the whole thread will not stuck. I hope this is fixed in the next version. Add Comment This message was sent by Atlassian JIRA (v7.3.1#73012-sha1:68837e3) ___ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev
