ch.qos.logback.classic.sift.SiftingAppender: 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 QOS.ch JIRA by h mahboobi, 1 year ago
This exception has no message.
ch.qos.logback.classic.sift.SiftingAppender:
at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:283)
at ch.qos.logback.classic.Logger.callAppenders(Logger.java:270)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:471)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:425)
at com.kishware.common.log.Slf4jLogger.debug(Slf4jLogger.java:47)
at com.kishware.core.framework.controller.PreOperationController.preOperationControl(PreOperationController.java:109)
at com.kishware.core.framework.controller.PreOperationController$1.call(PreOperationController.java:73)
at com.kishware.core.framework.controller.PreOperationController$1.call(PreOperationController.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

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.