Hi Sonya, Judging by the stack traces you provided your application is stuck in a blocking queue in your logging appender(s). Dropwizard 0.8 uses async appenders, that means the application doesn't write logs directly, but places them in a blocking queue, which is consumed by a background thread. Usually, it allows to improve latency when logging is slow. A strange thing that the threads are actually blocked in the queue. I believe, by default Logback discards INFO logging messages when the queue reaches 80% its capacity precisely to avoid blocking. Could you post your application's YAML configuration?
As a temporary solution you could try to increase the size of the queue (the queueSize parameter) or increase the discarding threshold (the discardingThreshold parameter​). Another option is to try to find a slow appender and replace it with a console one and see how it affects the application. I believe Dropwizard provides metrics for logging, so it should be possible to measure it in a staging environment. Artem -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
