Question
Anthem
US
Last activity: 3 Feb 2020 2:24 EST
Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor|Tomcat Error.
Hi Team,
Could you please help understand/resolve the following error observed in the Tomcat logs “Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor”.
Explored through online and PDN articles,but couldn’t find anything relevant.
Application Stack : MSSQL,PRPC731 and Tomcat 8.513
Error Stack below :
Hi Team,
Could you please help understand/resolve the following error observed in the Tomcat logs “Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor”.
Explored through online and PDN articles,but couldn’t find anything relevant.
Application Stack : MSSQL,PRPC731 and Tomcat 8.513
Error Stack below :
2020-01-15 18:42:22,617 [16.184-8147-exec-304] [ ] [ ] [ ] (here.cpr.AsynchronousProcessor) ERROR - Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor. java.lang.IllegalStateException: Response object no longer valid. This object has been cancelled at org.atmosphere.cpr.AtmosphereResourceImpl.getResponse(AtmosphereResourceImpl.java:424) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AtmosphereResourceImpl.getResponse(AtmosphereResourceImpl.java:436) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.DefaultBroadcaster.checkCachedAndPush(DefaultBroadcaster.java:1025) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.DefaultBroadcaster.cacheAndSuspend(DefaultBroadcaster.java:1416) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.DefaultBroadcaster.addAtmosphereResource(DefaultBroadcaster.java:1388) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AtmosphereResourceImpl.suspend(AtmosphereResourceImpl.java:401) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.interceptor.AtmosphereResourceLifecycleInterceptor.postInspect(AtmosphereResourceLifecycleInterceptor.java:145) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AsynchronousProcessor.postInterceptors(AsynchronousProcessor.java:374) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:230) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:115) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:68) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:2209) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:593) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.websocket.DefaultWebSocketProcessor.open(DefaultWebSocketProcessor.java:224) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.atmosphere.container.JSR356Endpoint.onOpen(JSR356Endpoint.java:252) ~[pratmosphere-runtime- Proprietary information hidden.jar:?] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init(WsHttpUpgradeHandler.java:133) ~[tomcat-websocket.jar:8.5.13] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:907) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1697) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:934) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:626) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:604) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:877) ~[tomcat-coyote.jar:8.5.13] at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:810) ~[tomcat-coyote.jar:8.5.13] at sun.nio.ch.Invoker.invokeUnchecked(Unknown Source) ~[?:1.8.0_151] at sun.nio.ch.Invoker$2.run(Unknown Source) ~[?:1.8.0_151] at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source) ~[?:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_151] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.5.13] at java.lang.Thread.run(Unknown Source) [?:1.8.0_151]
Thank you.
Pegasystems Inc.
US
I checked the error stack with the hotfix, not exactly the same although looks similar. PLus the hotfix is not verified. So use caution when proceed (e.g., ready to rollback if not working).
Anthem
US
Hotfix subject line refers to "Interceptor Atmosphere LifeCycle crashed websphere" and the reported issue has been observed with Tomcat.Not really how this hotfix helps (Is this compatible with Tomcat ?)
Moreover,its been 2 years since we have this Tomcat (version : 8.5.13) installed/running and started observing this error for the first time from yesterday.
Pegasystems Inc.
US
Pradeep,
Although the fix is generic (versus app server), but there is not enough evidence it is going to solve your issue. Now if this is only happening recently in your environment, are you aware of other potential env changes (versus Pega code, which I assume no changes)?
Anthem
US
Kevin,
Correction: This exception "Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor" has been observed to be happening from a while (not recent times).
1) I have obtained the following HFix-46226 and following are the only code changes (pratmosphere-runtime- Proprietary information hidden.jar).Is this applicable for Tomcat as well ? If not,Can we have a similar hotfix spinned up for Tomcat (in specific) ?
2) In the first place,What factors can trigger this issue?
3) Can a tomcat upgrade help resolve this ? If yes,any recommended version ?
4)Is this an impacting or non-impacting error ? If not impacting,how can this be suppressed with the current tomcat version ?
Please suggest.
Thank you.
Pegasystems Inc.
US
The fix is mainly diagnostic, I would be surprised it actually fixes the issue (it is generic though). Often times, the issue can be app server related due to its own web socket implementation. Try to upgrade tomcat to see if it is still there first, especially this happens frequently in your current environment.
Anthem
US
Hi Kevin,
Please suggest regarding the below highlighted details.
3) Can a tomcat upgrade help resolve this ? If yes,any recommended version ?
4) Is this an impacting or non-impacting error ? If not impacting,how can this be suppressed with the current tomcat version ?
Pegasystems Inc.
US
3) no, you would have to try yourself. I would try the latest tomcat 8 to see first.
4) This may impact Operator Presence features: https://community.pega.com/knowledgebase/release-note/operator-presence-record-tracks-disconnected-status-operators
Anthem
US
Hi Kevin,
Regarding point 4,are you referring that Operator Presence is the only OOTB functionality which uses web sockets ? If yes,help understand this criteria.Based on which, we might need to find out if we have any custom functionalities which uses web sockets as well.
On a side note,please confirm if these errors "Interceptor Atmosphere LifeCycle crashed. Processing will continue with other interceptor" can lead to JVM thread's exhaustion ?
Anthem
US
Hi Moderators,
Please help followup with Kevin.
Thank you.