Details
-
Type: Bug
-
Status: Closed
-
Priority: Blocker
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02
-
Fix Version/s: EE-3.3.0.GA_P02
-
Component/s: Push Library, Push Server
-
Labels:None
-
Environment:Tomcat 7.0.54, ActiveMQ 5.1.0, ICEfaces, ICEpush, EPS
Description
I deployed EPS and Poll to a stand-alone environment of Tomcat and ActiveMQ and letting the blocking connection idle results into an IllegalStateException:
May 27, 2014 2:32:07 PM org.icepush.BlockingConnectionServer run
WARNING: Exception caught on org.icepush.BlockingConnectionServer TimerTask.
java.lang.RuntimeException: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.
at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:180)
at org.icepush.BlockingConnectionServer.run(BlockingConnectionServer.java:109)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.
at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:535)
at org.apache.catalina.core.AsyncContextImpl.complete(AsyncContextImpl.java:92)
at org.icepush.servlet.AsyncAdaptingServlet$AsyncRequestResponse.respondWith(AsyncAdaptingServlet.java:69)
at com.icesoft.icepush.AdjustHeartbeatServer$HeartbeatRequest.respondWith(AdjustHeartbeatServer.java:66)
at org.icepush.SequenceTaggingServer$TaggingRequest.respondWith(SequenceTaggingServer.java:67)
at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:177)
... 3 more
May 27, 2014 2:32:07 PM org.icepush.BlockingConnectionServer run
WARNING: Exception caught on org.icepush.BlockingConnectionServer TimerTask.
java.lang.RuntimeException: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.
at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:180)
at org.icepush.BlockingConnectionServer.run(BlockingConnectionServer.java:109)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.
at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:535)
at org.apache.catalina.core.AsyncContextImpl.complete(AsyncContextImpl.java:92)
at org.icepush.servlet.AsyncAdaptingServlet$AsyncRequestResponse.respondWith(AsyncAdaptingServlet.java:69)
at com.icesoft.icepush.AdjustHeartbeatServer$HeartbeatRequest.respondWith(AdjustHeartbeatServer.java:66)
at org.icepush.SequenceTaggingServer$TaggingRequest.respondWith(SequenceTaggingServer.java:67)
at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:177)
... 3 more
Issue Links
- depends on
-
PUSH-293 AsyncAdaptingServlet and ThreadBlockingAdaptingServlet should take the up-to-date heartbeatInterval value into account for the timeout
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Back-porting completed.