Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Documentation
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-9237Restructure sections on clustering and session document service KULRICE-6031Document implementation/configuration guides KULRICE-1269Document Session Enable Document feature KULRICE-2209KSB failover implementation is inadequate KULRICE-9272Instructions to setting up a Rice cluster are incorrect (installation guide) KULRICE-6172Document the Implementation Considerations guide for KNS KULRICE-6125Document the Implementation Considerations guide for KSB KULRICE-12270Disable failover on topic messages in KSB KULRICE-6215 Add information regarding Implementation Considerations guide for Rice -
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Include in Release Notes?:Yes
Description
As discussed in the KTI on March 13, 2013. We are planning to disable/remove SessionDocumentService. There are other solutions for session replication/failover. Including features built natively into Tomcat and other j2ee servlet/application containers. Also solutions like Terracota Web-sessions.
Issue Links
- relies on
-
KULRICE-9148 Disable SessionDocumentService in the KNS
-
Given the date changes for 2.1.4/2.2.2, I'm moving this back to 2.1.4/2.2.2.