[
https://issues.jboss.org/browse/ISPN-1285?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1285:
----------------------------------------
This is a bit tricky actually. One way to get around it would be to assign a new flag that
the Hot Rod client can pass to let the server know that the 0/0 lifespan/maxIdle
parameters are 0 because the client didn't pass any, and so the server could use the
default expiry/lifespan values. However, creating this new flag would mean changing the
protocol. Checking more options...
Cache entries stored via Hot Rod client with default expiry remain in
cache
---------------------------------------------------------------------------
Key: ISPN-1285
URL:
https://issues.jboss.org/browse/ISPN-1285
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.0.0.CR8
Reporter: Martin Gencur
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Default values for expiration specified via Infinispan configuration file (tag
<expiration lifespan="2000" maxIdle="1000" />) do not influence
real lifespan of cache entries stored via the Hot Rod client.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira