[logback-user] Logback Lock causing the app to lock up

[Greg Nitro]

To follow up for others' sake who may be experiencing:

We've added an async appender around the stdout appender. We found some
issue with the docker containers hosting the apps with the issue I reported
where Heka (which forwards logs from STDOUT to our logging aggregators) was
queueing up and not flushing

So we are investigating that issue further but it's clearly not a problem
with Logback itself.. or at least as far as I can tell.

-greg

On Mon, Apr 11, 2016 at 2:56 PM, Greg Nitro <gregnitro225 at gmail.com> wrote:

> Hi Ceki,
>
> Thanks for the quick response.  Attached is the xml file with the
> configuration.
>
> -greg
>
>
>
> On Mon, Apr 11, 2016 at 12:48 PM, Ceki Gulcu <ceki at qos.ch> wrote:
>
>>
>> Can you please post your configuration file as well?
>>
>>
>> On 4/11/2016 19:59, Greg Nitro wrote:
>>
>>> Hi,
>>>
>>> We are using Logback 1.1.3, and observed through jstack that quite a few
>>> threads were blocked in OutputStreamAppender.subAppend waiting to obtain
>>> the lock.
>>>
>>> This is a Play Framework app running in a dockerized environment,
>>> configured to log to STDOUT and papertrail.
>>>
>>> Stack trace:
>>>
>>> "New I/O worker #23" #75 prio=5 os_prio=0 tid=0x00007f6fc9764000
>>> nid=0xaa waiting for monitor entry [0x00007f6edd3e7000]
>>>     java.lang.Thread.State: BLOCKED (on object monitor)
>>> at
>>>
>>> ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:211)
>>> - waiting to lock <0x00000000ab0f8f50> (a
>>> ch.qos.logback.core.spi.LogbackLock)
>>> at
>>>
>>> ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:103)
>>> at
>>>
>>> ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88)
>>> at
>>>
>>> ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48)
>>> at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:273)
>>> at ch.qos.logback.classic.Logger.callAppenders(Logger.java:260)
>>> at
>>> ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:442)
>>> at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:396)
>>> at ch.qos.logback.classic.Logger.info
>>> <http://ch.qos.logback.classic.Logger.info>(Logger.java:600)
>>> at play.api.LoggerLike$class.info <http://class.info>(Logger.scala:93)
>>> at play.api.Logger$.info(Logger.scala:167)
>>>
>>> Any suggestions on what may be going on here?
>>>
>>> Thanks
>>> -greg
>>>
>>>
>>> _______________________________________________
>>> logback-user mailing list
>>> logback-user at qos.ch
>>> http://mailman.qos.ch/mailman/listinfo/logback-user
>>>
>>> _______________________________________________
>> logback-user mailing list
>> logback-user at qos.ch
>> http://mailman.qos.ch/mailman/listinfo/logback-user
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20160413/604bb0f8/attachment.html>