Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2
-
Fix Version/s: 1.8.3, 1.8.2-EE-GA_P02
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces, Liferay
-
ICEsoft Forum Reference:
Description
Occasionally push events will fail to be delivered. SessionRenderer.render() is known to be called but the session appears to be no longer in the group.
This is believed to be due to the WeakReference referring to the sesionID in GroupAsyncRenderer:
if (!contains(object)) {
if (group.add(new WeakReference(object))) {
it is not necessary to retain the sessionID String with only a WeakReference, unlike the previous implementation where a reference to the session object was maintained.
Issue Links
- is duplicated by
-
ICE-4434
Ajax push doesn't work anymore after a page change in liferay portal
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This bug does not seem to appear in applications that are using the Renderable API (thereby avoiding the weak reference to the sessionID).
This is my assumption:
- Whenever the session is decorated (a lot of frameworks do that), what is added as a WeakReference within the GroupAsyncRenderer's add(Object) method is not the "real" session object but rather the wrapped one which is thrown away and hence becomes weakly reachable and might be removed by the house-keeping mechanism within the GroupAsyncRenderer.
This might be an explanation why push is not working from time to time and a well know workaround is to add the session to a render group more frequently.
As Ted notes, now that we've moved away from relying on sessions and now use session ids, we likely don't require wrapping the key in a WeakReference any longer as it would potentially cause the noted problem if the key itself does not live as long as the session.
Micha, please let us know whether the code change of removing the WeakReference resolves the problem in your application.
...or attach a test-case that can be used to reproduce the issue and verify the fix.
Re-opening to apply fix.
Applying modified version of the fix that was sent to support customer.
Assigning to Deryk for dispatch. Micha will potentially provide a test case.