Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Bug 1285472
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh86 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1285472
-
Add global state persistence configuration and allow internal caches to use it
Summary:
Add global state persistence configuration and allow internal caches to use it
Keywords
:
Status
:
VERIFIED
Alias:
None
Product:
JBoss Data Grid 6
Classification:
JBoss
Component:
Infinispan
Sub Component:
---
Version:
6.6.0
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
unspecified
Target Milestone:
ER3
Target Release
:
6.6.0
Assignee:
Tristan Tarrant
QA Contact:
Martin Gencur
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2015-11-25 16:45 UTC by
Adrian Nistor
Modified:
2022-05-31 22:24 UTC (
History
)
CC List:
2 users
(
show
)
jdg-bugs
vjuranek
Fixed In Version:
Doc Type:
Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type:
Bug
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
ISPN-3926
0
Major
Resolved
The Internal Cache Registry needs to be persistent
2018-04-23 19:19:29 UTC
Red Hat Issue Tracker
ISPN-5742
0
Major
Resolved
Add global persistent state path configuration
2018-04-23 19:19:30 UTC
Red Hat Issue Tracker
ISPN-5851
0
Major
Resolved
Split global state path specification in persistent and temporary
2018-04-23 19:19:29 UTC
Description
Adrian Nistor
2015-11-25 16:45:18 UTC
Note
You need to
log in
before you can comment on or make changes to this bug.