[logback-user] RES: STUCK threads with Logback

[Fabiano, Lucas]

Hi Chris,

I saw something similiar when the logback had to reload the configuration file.
I was using tomcat in localhost and I had to force the server to stop.

Good Lucky!

  Lucas Fabiano
  Arquitetura Corporativa
  Tel. 5511 2847-9523
  lucas.fabiano at br.experian.com
  serasaexperian.com.br

-----Mensagem original-----
De: Logback-user [mailto:logback-user-bounces at qos.ch] Em nome de David Roussel
Enviada em: quarta-feira, 13 de maio de 2015 13:34
Para: logback users list
Assunto: Re: [logback-user] STUCK threads with Logback

Hi Chris,

I always use an async spender so that my application logic is not delayed by logback trying to write synchronously to disk.

David

> On 13 May 2015, at 16:07, Kantzer, Chris E <ckantzer at cxloyalty.com> wrote:
>
> Hello,
> We are getting some stuck threads in our Prod apps that seem to point to logback as the culprit.  It only took a few moments to realize we have been lax with our logging statements and we were logging a huge amount of (unnecessary) lines.  We are cutting back significantly the number of logged lines in the hopes that it solves the issue.
>
> My question:  Is there anything else we should investigate as a possible reason for logback causing stuck threads OTHER than excessive logging?  I can post the stack trace if needed.
>
> Thanks,
> Chris Kantzer
>
> _______________________________________________
> 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

________________________________

This email and any attachments are for the exclusive and confidential use of the named intended recipient(s) and may be legally privileged. Any review, re-transmission, dissemination or any other use of its contents, or taking of any action in reliance upon this information by persons and/or entities other than the named intended recipient(s) is strictly prohibited. If you have received this communication in error, please send this communication back to the sender, disregard its contents, and promptly delete the original message and any copy of it from your computer systems. The misuse of this message will be dealt according to company rules and current legislation. This message expresses the sender’s point of view about the topics described and not necessarily expresses Serasa Experian’s opinion about them.

As informações contidas nesta mensagem e no(s) arquivo(s) anexo(s) são endereçadas exclusivamente à(s) pessoa(s) e/ou instituição(ões) acima indicada(s), e podem conter dados confidenciais. É expressamente proibido a pessoas não autorizadas, sob qualquer forma ou pretexto, utilizá-las, divulgá-las, alterá-las, de forma impressa ou copiada, total ou parcialmente. Caso tenha recebido esta mensagem erroneamente, por favor, notifique o remetente e providencie imediata exclusão da original e de qualquer cópia. O uso impróprio será tratado conforme as normas da empresa e da legislação em vigor. Esta mensagem expressa o posicionamento pessoal do subscritor e não reflete necessariamente a opinião da Serasa Experian.