Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist.
Issue
- During the shutdown of EAP, the following warning appears in the log:
~~~
WARNING [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 110) Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist.
~~~ - Can I ignore this warning during EAP shutdown?
- What causes the warning message?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
