Details
Bug
Critical
Description
Tomcat seems to be getting into a thread-leak problem when having a fair amount of asynchronous ICEfaces Portlets on one single Portal page. Eventually it is running out of its 150 threads in the thread pool.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The problem in this case was that when an incoming request was received put there was a pending request as well, the pending request was replaced by the new request without handling the pending request first, by replying with an empty response. This caused the pending request to get lost in the void, but holding on to a precious Tomcat thread.
Now the pending requests gets satisfied first with an empty response, thus releasing the Tomcat thread, and then the new incoming request is set as the new pending request. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - The problem in this case was that when an incoming request was received put there was a pending request as well, the pending request was replaced by the new request without handling the pending request first, by replying with an empty response. This caused the pending request to get lost in the void, but holding on to a precious Tomcat thread.
Now the pending requests gets satisfied first with an empty response, thus releasing the Tomcat thread, and then the new incoming request is set as the new pending request. Marking this one as FIXED.
Changed Fix Version(s) to 1.7-Beta 1