Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6, 1.6.1
-
Fix Version/s: 1.6.1
-
Component/s: None
-
Labels:None
-
Environment:ICEfaces Asynchronous HTTP Server 1.6.0, 1.6.0a & 1.6.1
Description
Currently with the ICEfaces Asynchronous HTTP Server 1.6.x releases, one MessageServiceClient is created for each Session, which results in one MessageReceiver thread being created for each Session as well! We should look into trying to achieve the goal of having only one MessageServiceClient per Servlet Context that can be used by all Sessions. This JIRA case is used to introduce a quick fix for ICEfaces Asynchronous HTTP Server 1.6.1a. The final fix is targeted for ICEfaces Asynchronous HTTP Server 1.7.0 and mentioned in ICE-2073.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The fix for this issue is targeted for ICEfaces Asynchronous HTTP Server 1.6.1a.
Show
Jack Van Ooststroom
added a comment - The fix for this issue is targeted for ICEfaces Asynchronous HTTP Server 1.6.1a.
This should be fixed in a better nicer way for ICEfaces 1.7. However, this JIRA case was specifically intended for a quick fix. The MessageServiceClient is now a static class member of AsyncHttpServerAdaptingServlet instead of a "normal" class member. This results in having only one MessageServiceClient per application, instead of per session. Marking this one as FIXED.