java.lang.IllegalStateException

Cannot add new shutdown hook as this is not started. Current state: STOPPED 2016-09-14T20:41:24.116823+00:00 app[web.1]: at org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.addShutdownCallback(DefaultShutdownCallbackRegistry.java:113) 2016-09-14T20:41:24.116825+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.addShutdownCallback(Log4jContextFactory.java:273) 2016-09-14T20:41:24.116828+00:00 app[web.1]: at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:216) 2016-09-14T20:41:24.116829+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:145) 2016-09-14T20:41:24.116830+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41) 2016-09-14T20:41:24.116831+00:00 app[web.1]: at org.apache.logging.log4j.LogManager.getContext(LogManager.java:182) 2016-09-14T20:41:24.116831+00:00 app[web.1]: at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103) 2016-09-14T20:41:24.116832+00:00 app[web.1]: at org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39) 2016-09-14T20:41:24.116833+00:00 app[web.1]: at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42) 2016-09-14T20:41:24.116834+00:00 app[web.1]: at org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via GitHub by Reedyuk
    ,
  • Stack trace

    • java.lang.IllegalStateException: Cannot add new shutdown hook as this is not started. Current state: STOPPED 2016-09-14T20:41:24.116823+00:00 app[web.1]: at org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.addShutdownCallback(DefaultShutdownCallbackRegistry.java:113) 2016-09-14T20:41:24.116825+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.addShutdownCallback(Log4jContextFactory.java:273) 2016-09-14T20:41:24.116828+00:00 app[web.1]: at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:216) 2016-09-14T20:41:24.116829+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:145) 2016-09-14T20:41:24.116830+00:00 app[web.1]: at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41) 2016-09-14T20:41:24.116831+00:00 app[web.1]: at org.apache.logging.log4j.LogManager.getContext(LogManager.java:182) 2016-09-14T20:41:24.116831+00:00 app[web.1]: at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103) 2016-09-14T20:41:24.116832+00:00 app[web.1]: at org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39) 2016-09-14T20:41:24.116833+00:00 app[web.1]: at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42) 2016-09-14T20:41:24.116834+00:00 app[web.1]: at org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40) at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5478) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.