Support Article
Exceptions generated in the logs during a server restart
SA-61509
Summary
Exceptions generated in the logs during a server restart.
Error Messages
- ERROR - Real error: Unable to configure jsr356 at that stage. ServerContainer is null
java.lang.IllegalStateException: Unable to configure jsr356 at that stage. ServerContainer is null - If you have more than one Connector enabled, make sure they both use the same protocol, e.g NIO/APR or HTTP for all. If not, org.atmosphere.container.BlockingIOCometSupport will be used and cannot be changed.
java.lang.IllegalStateException: JBoss failed to detect this is a Comet application because the APR Connector is not enabled.
Make sure atmosphere-compat-jboss.jar is not under your WEB-INF/lib and You must use the atmosphere-native-runtime dependency in order to use native Comet Support
there is no context.xml under WEB-INF
at org.atmosphere.container.JBossWebCometSupport.<clinit>(JBossWebCometSupport.java:53)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Steps to Reproduce
Restart the server.
Root Cause
Pega 7.2.2 introduced real-time notifications using Comet technologies such as WebSocket and Long Polling. An error stack displays if the application server does not support WebSocket and non-blocking Long Polling.
Resolution
As a local-change, enable WebSocket.
Published August 1, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.