Lifespan works differently when the specified lifespan is bigger than 30 days in JDG 7.1/7.2/7.3
Issue
- JDG 6.6.2 and JDG 7.2.3 behave differently when the specified lifespan is bigger than 30 days
- An entry is immediately expired when the specified lifespan is bigger than 30 days in JDG 7.1/7.2/7.3. But, this issue does not happen in JDG 6.6.2. For example, when 2592001 seconds (== 30 days + 1 seconds) is specified to lifespan, an entry is created with the specified lifespan in JDG 6.6.2, but the created entry is immediately expired in JDG 7.2.3.
Environment
- Red Hat JBoss Data Grid (JDG)
- 6.x
- 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
