tracker issue : CF-3361502

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

No setting in cluster admin to enable session replication

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Dave Ferguson / Dave Ferguson (Dave Ferguson)

Created: 11/07/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final / 288150

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 1

The ability to enable / disable session replication is missing from the cluster administrator.  This setting was there in CF9/8 but is now gone in 10.

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

Watson Bug ID:	3361502

Deployment Phase:	Release Candidate

Keywords:
FixTested


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

Attachments:

Comments:

Yeah, I can't find out where to set this, if "on the UI where I'd expect it to be" isn't the case on CF10 "by design" -- Adam
Vote by External U.
17274 | November 07, 2012 11:43:22 AM GMT
When stickysession is enabled the session is not replicated and when stickysession is disabled the session is automatically replicated.
Comment by Asha K.
17270 | January 20, 2014 08:51:08 AM GMT
Thank-you for stating the obvious, Asha. I think what you say there is the entire reason this ticket was raised. So it's not an explanation, it's just a description of the problem. This justification holds little water: session replication should not be dependent on server clustering. What happens when a server in the cluster fails? It'd be nice to not have the sessions vanish. Which is what you seem to think is "OK". But only "OK" in CF10... obviously given it didn't work that way in CF [previous] someone in those days had their head screwed on. To their neck, I mean. -- Adam
Comment by External U.
17271 | January 26, 2014 05:22:57 PM GMT
Is this correct: State Closed Status Fixed If so: cool! Cheers. -- Adam
Comment by External U.
17272 | February 03, 2014 09:35:33 AM GMT
The fix has been verified, and will be available in a future release.
Comment by Immanuel N.
17273 | February 03, 2014 11:10:15 PM GMT