tracker issue : CF-4195152

select a category, or use search below
(searches all categories and all time range)

same as bug 4176297 but losing session scope also

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Aaron Shurmer / Aaron Shurmer (Aaron Shurmer)

Created: 10/05/2016

Components: Web Socket

Versions: 2016

Failure Type: Data Loss

Found In Build/Fixed In Build: CF2016_Update2 /

Priority/Frequency: Major / Some users will encounter

Locale/System: ALL / Win 2008 Server x64

Vote Count: 0

same as bug 4176297 but losing session scope also - fix in updater 3 doesn't fix the issue with session, only request. not sure if there are other random scopes also disappearing...

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4195152

Reason:	PRNeedInfo

External Customer Info:
External Company:  
External Customer Name: Aaron Shurmer
External Customer Email:  
External Test Config: My Hardware and Environment details:


  1. June 02, 2017 00:00:00:


Hi Aaron, We have tested it at our end and it is working for us in the case of session scope. Can you please share your test case with us?
Comment by Kailash B.
1686 | October 06, 2016 01:27:25 AM GMT
did you get the attached file? not sure it worked....
Comment by Aaron S.
1687 | June 02, 2017 12:35:42 AM GMT
@Aaron - It doesn't look like the file came through. Can you reattach?
Comment by Vamseekrishna N.
1688 | June 02, 2017 04:32:14 AM GMT
Hi Aaron, The old test case which was shared in 2016, the onSessionEnd function had two arguments missing. If you give those, the test case passes. Syntax should be: function onSessionEnd(sessionScope, applicationScope) { //Your code } For the new code you shared on 02 June, 2017, the session scope is not at all present. Its most likely for request scope. That test cases is correct for the bug with number : #4176297, not for this bug.
Comment by Kailash B.
1689 | June 14, 2017 08:37:37 AM GMT
? not using onsessionend, it's onrequestend where the issue is in the attached test case..
Comment by Aaron S.
1690 | June 19, 2017 02:08:37 AM GMT
Hi Aaron, We have already fixed the case for onRequestEnd. This bug corresponds to onSessionEnd. Can you please verify this? I have already mentioned the fix for onSessionEnd in the comments. Thanks, Kailash
Comment by Kailash B.
1691 | September 11, 2017 04:48:27 AM GMT
The issue with the onRequestEnd was already fixed. This bug was raised for onSessionScope. The user was not using a few onSessionScope attributes required. Have mentioned that in the comments. There was another bug with respect to sessions. We have fixed that for the next update release. hence, closing this bug as a duplicate of that. Have linked this bug to the other bug as well. If the user is still facing similar issue, will reopen this case.
Comment by Kailash B.
1692 | September 17, 2017 06:14:14 PM GMT