| Summary: | simplify Externalize HTTP Session | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Shay Matasaro <smatasar> |
| Component: | Documentation | Assignee: | jdg-docs <jdg-docs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.6.1 | CC: | dereed, jdg-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
Build Name: 23149, Administration and Configuration Guide-6.6
Build Date: 08-09-2016 09:25:13
Topic ID: 44411-776217 [Specified]
|
|
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
At the least a separate cache config is needed (and jboss-web.xml to point to it), because the JDG cache name is hard-coded, and can't be shared between apps. |
Title: Externalize HTTP Session from JBoss EAP 6.4 and later to JBoss Data Grid The docs describe the addition of a new cache container and cache where externalization can be done by simply adjusting the existing web cache (repl or dist) for example : <cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan" statistics-enabled="true"> <transport lock-timeout="60000"/> <replicated-cache name="repl" mode="ASYNC" batching="true"> <file-store/> </replicated-cache> <replicated-cache name="sso" mode="SYNC" batching="true"/> <distributed-cache name="dist" l1-lifespan="0" mode="ASYNC" batching="true"> <file-store/> </distributed-cache> </cache-container> Also there jboss-web.xml is not a must, only needed in order to fine tune settings