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

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

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: