Chris, Yes it did just to be on the safe side. There is a stackoverflow question about it, perhaps with an answer from me. It's been a while since I did it. David
On 13 May 2015, at 17:45, Kantzer, Chris E <ckantzer@cxloyalty.com> wrote:
Lucas, I do have scan set to true in my config, but we were not updating the config at the time of the stuck threads. Thanks though.
David, I will look into the asyncappender. Did you have to add the hooks for app shutdown or post shutdown cleanup?
-----Original Message----- From: Logback-user [mailto:logback-user-bounces@qos.ch] On Behalf Of David Roussel Sent: Wednesday, May 13, 2015 12:34 PM To: logback users list Subject: 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@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@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user