High CPU usage in SessionExpirationScheduler thread and/or large amount of ERROR and WARN logs after restarting EAP 8.1.x

Issue

• After restarting EAP 8.1.x instances that are part of an Infinispan cluster, CPU usage for those instances spikes and logs similar to the following are being continuously output:

  ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (thread-9,...) ISPN000136: Error executing command LockControlCommand on Cache '<deployment>', writing keys []: org.infinispan.commons.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key SessionMetaDataKey(<session id>) and requestor GlobalTransaction{...}. Lock is held by GlobalTransaction{...}
  WARN  [org.infinispan.CLUSTER] (thread-9,...) ISPN000071: Caught exception when handling command LockControlCommand{cache=<deployment>, keys=[SessionMetaDataKey(<session id>)], flags=[ZERO_LOCK_ACQUISITION_TIMEOUT, FORCE_WRITE_LOCK], unlock=false, gtx=GlobalTransaction{...}}: org.infinispan.commons.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key SessionMetaDataKey(<session id>) and requestor GlobalTransaction{...}. Lock is held by GlobalTransaction{...}
  ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (thread-9,...) ISPN000136: Error executing command LockControlCommand on Cache '<deployment>', writing keys []: org.infinispan.commons.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key SessionMetaDataKey(<session id>) and requestor GlobalTransaction{...}. Lock is held by null
  WARN  [org.infinispan.CLUSTER] (thread-9,...) ISPN000071: Caught exception when handling command LockControlCommand{cache=<deployment>, keys=[SessionMetaDataKey(<session id>)], flags=[ZERO_LOCK_ACQUISITION_TIMEOUT, FORCE_WRITE_LOCK], unlock=false, gtx=GlobalTransaction{...}}: org.infinispan.commons.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key SessionMetaDataKey(<session id>) and requestor GlobalTransaction{...}. Lock is held by null
  

• After restarting EAP 8.1.x instances that are part of an Infinispan cluster, the SessionExpirationScheduler is showing high CPU usage.