Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by Javaru
, 1 year ago
via QOS.ch JIRA by Mark Vedder, 1 year ago
This exception has no message.
ch.qos.logback.core.spi.LogbackLock at ch.qos.logback.core.BasicStatusManager.add(BasicStatusManager.java:59) at ch.qos.logback.core.spi.ContextAwareBase.addStatus(ContextAwareBase.java:79) at ch.qos.logback.core.spi.ContextAwareBase.addInfo(ContextAwareBase.java:84) at ch.qos.logback.core.rolling.helper.Compressor.gzCompress(Compressor.java:193) at ch.qos.logback.core.rolling.helper.Compressor.compress(Compressor.java:55) at ch.qos.logback.core.rolling.helper.CompressionRunnable.run(CompressionRunnable.java:33) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722)