Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Fix Version/s: 3.0
-
Component/s: None
-
Labels:None
-
Environment:server
-
ICEsoft Forum Reference:
Description
philipp.grasboeck: "We found a memory leak issue using ICEfaces 2.0.1 and 2.0.2 that arises if icepush is deployed, synchronousUpdate=false, but our app doesn't use ICEpush features at all.
The pushIDMap in org.icepush.LocalPushGroupManager grows and grows and doesn't seem to get evicted, I had a look at the source code, it has some expiration for the push ids that doesn't seem to take effect in our case."
The pushIDMap in org.icepush.LocalPushGroupManager grows and grows and doesn't seem to get evicted, I had a look at the source code, it has some expiration for the push ids that doesn't seem to take effect in our case."
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The applied fix triggers the scanning for pushID and group expiry on addMember() and push() method invocations. This way the expiry is running even if the blocking connection is not activated.
Show
Mircea Toma
added a comment - - edited The applied fix triggers the scanning for pushID and group expiry on addMember() and push() method invocations. This way the expiry is running even if the blocking connection is not activated.
When the blocking connection is not running the pushId and group scanning for expiry is not activated. The memory leak is triggered when ICEfaces creates new pushIDs on every page load but ICEpush will not expire them.