Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded ------------------------------------------------------------------------- Key: ISPN-9582 URL: https://issues.jboss.org/browse/ISPN-9582 Project: Infinispan Issue Type: Bug Affects Versions: 9.4.0.CR3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Major Fix For: 9.4.8.Final In embedded mode, specifying 0 for lifespan or maxIdle results in immediate expiration. In Hot Rod, however, 0 results in the entry using the default server-side expiration. This was done in order to not introduce a protocol change at the time. The 2.2 protocol introduced timeunit support with special values for default and infinity. We should therefore not override a user-specified value of 0 with "default".