Expiration is not working under some circumstances with AtomicMap

When AtomicMaps are used with writeskew (+ simple versioning) lifespan from the config file is ignored and instead get infinite lifespan for the entries.

The configured default value is used if I any of the following parameters change

• Disable write skew checks
• Use a normal put (not atomic maps)
• Do not start transactions first.