ICEpush
  1. ICEpush
  2. PUSH-137

Memory leak with ICEpush deployed but not used

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Alpha3
    • Fix Version/s: 3.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      server

      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."

        Activity

        Mircea Toma created issue -
        Mircea Toma made changes -
        Field Original Value New Value
        Assignee Mircea Toma [ mircea.toma ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #24912 Tue Jun 28 05:24:07 MDT 2011 mircea.toma PUSH-137 Trigger the scanning for pushID and group expiry on addMember() and push() method invocations.
        Files Changed
        Commit graph MODIFY /icepush/trunk/core/src/main/java/org/icepush/LocalPushGroupManager.java
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #24913 Tue Jun 28 05:37:49 MDT 2011 mircea.toma PUSH-137 Update library to rev. 24912.
        Files Changed
        Commit graph MODIFY /icefaces2/trunk/icefaces/lib/icepush.jar
        Hide
        Mircea Toma added a comment -

        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.

        Show
        Mircea Toma added a comment - 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.
        Hide
        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.

        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.
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Mircea Toma made changes -
        Salesforce Case []
        Fix Version/s 2.1 [ 10259 ]
        Fix Version/s 2.0-Beta [ 10232 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Mircea Toma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: