is this error storage related ?

[Kevin Foote]

I’m tracking down a newly introduced issue that has appeared locally since moving to 3.2.1 and hazelcast storage. I’m just looking to vet my thoughts that 
this is due to the storage mechanics and not some errant setting WRT the sessions in general. 

Here is the error I get in the logs… 

2016-01-29 08:43:55,118 - DEBUG [net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:126] - [my.ip] - Profile Action PopulateAuthenticationContext: Installing custom PrincipalEvalPredicateFactoryRegistry into AuthenticationContext
2016-01-29 08:43:55,118 - DEBUG [net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:167] - [my.ip] - Profile Action PopulateAuthenticationContext: Installed 1 authentication flows into AuthenticationContext
2016-01-29 08:43:55,118 - DEBUG [net.shibboleth.idp.session.impl.StorageBackedSessionManager:707] - [my.ip] - Performing primary lookup on session ID bbd2cdb85ba41117918adc88c1b06939a728d85bcec3d629e656ae11901b3904
2016-01-29 08:43:55,119 - DEBUG [net.shibboleth.idp.session.impl.StorageBackedIdPSession:90] - [my.ip] - Updating expiration of master record for session bbd2cdb85ba41117918adc88c1b06939a728d85bcec3d629e656ae11901b3904 to 2016-01-29T09:43:55.119-08:00
2016-01-29 08:43:55,121 - DEBUG [net.shibboleth.idp.session.impl.StorageBackedIdPSession:528] - [my.ip] - Loading AuthenticationResult for flow authn/Password in session bbd2cdb85ba41117918adc88c1b06939a728d85bcec3d629e656ae11901b3904
2016-01-29 08:43:55,122 - ERROR [net.shibboleth.idp.authn:-2] - [my.ip] - Uncaught runtime exception
net.shibboleth.utilities.java.support.logic.ConstraintViolationException: Last activity instant must be greater than 0
        at net.shibboleth.utilities.java.support.logic.Constraint.isGreaterThan(Constraint.java:81)
2016-01-29 08:43:55,122 - WARN [org.opensaml.profile.action.impl.LogEvent:76] - [my.ip] - An error event occurred while processing the request: RuntimeException


It looks to me like this is trying to up date the idp session with the latest time-stamp info and the times are not different enough to allow this so the exception is thrown.. 

 

--------
thanks
 kevin.foote