ch.qos.logback.core.spi.LogbackLock: This exception has no message.

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
, 10 months ago
via JIRA by Mark Vedder, 1 year ago
This exception has no message.
at ch.qos.logback.core.BasicStatusManager.add(
at ch.qos.logback.core.spi.ContextAwareBase.addStatus(
at ch.qos.logback.core.spi.ContextAwareBase.addInfo(
at ch.qos.logback.core.rolling.helper.Compressor.gzCompress(
at ch.qos.logback.core.rolling.helper.Compressor.compress(
at java.util.concurrent.Executors$
at java.util.concurrent.FutureTask$Sync.innerRun(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.