Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

java.lang.IllegalStateException in the application server logs

SA-38264

Summary



After user upgrade to Pega 7.2.2, the exception "java.lang.IllegalStateException: Unable to configure jsr356 at that stage. ServerContainer is null" is thrown during the application Server startup.

The application is running on WebLogic Server Version: 12.1.3.0.0 with Jap Version Java HotSpot(TM) 64-Bit Server VM Version 24.71-b01.

As user's application does not support mobile devices, they would like to know how the above exception can be disabled


Error Messages



2017-05-05 14:36:55,117 [] [ STANDARD] [ ] [ ] (e.container.JSR356AsyncSupport) ERROR - WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Oracle WebLogic Server Module Dependencies 12.1 Tue Mar 11 15:35:15 MDT 2014 WebLogic Jersey Server Integration 3.0 Fri Feb 21 10:55:11 UTC 2014 must use JDK 1.8+ with WebSocket

2017-05-05 14:36:55,119 [] [ STANDARD] [ ] [ ] (pr.DefaultAsyncSupportResolver) 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
at org.atmosphere.container.JSR356AsyncSupport.<init>(JSR356AsyncSupport.java:51)
at org.atmosphere.container.JSR356AsyncSupport.<init>(JSR356AsyncSupport.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)


Steps to Reproduce



Upgrade to Pega 7.2.2.

During server start up the exception can be seen in the server logs


Root Cause



A defect or configuration issue in the operating environment.

As user's applications does not support mobile devices, the push notifications feature does not work.

Resolution



Perform the following local-change:

Set the value for "server-push/enabled" to 'false' in prconfig.xml file to disable the feature.

Published June 29, 2017 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us