scenario: - configure EAP to store sessions on JDG - start JDG - start EAP - login to eap(session created) - jdg stats shows 1 entry - shutdown EAP - startup EAP - jdg stats shows 1 entry - shutdown EAP - jdg stats shows 0 entries So when EAP i shutdown for the second times it removes exiting session key. During the second EAP shutdown , the JDG logs show : 23:50:46,076 TRACE [org.infinispan.interceptors.InvocationContextInterceptor] (HotRodServerWorker-1) Invoked with command RemoveCommand{key=[B@1086376f, value=null, flags=null, valueMatcher=MATCH_ALWAYS} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@5ba160e2] 23:50:46,077 TRACE [org.infinispan.statetransfer.StateTransferInterceptor] (HotRodServerWorker-1) handleNonTxWriteCommand for command RemoveCommand{key=[B@1086376f, value=null, flags=null, valueMatcher=MATCH_ALWAYS}, topology id -1 23:50:46,077 TRACE [org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] (HotRodServerWorker-1) Are (node/DAL) we the lock owners for key '[B@1086376f'? true 23:50:46,077 TRACE [org.infinispan.util.concurrent.locks.LockManagerImpl] (HotRodServerWorker-1) Attempting to lock [B0x0301fe033c000054..[48] with acquisition timeout of 15000 millis 23:50:46,078 TRACE [org.infinispan.util.concurrent.locks.containers.ReentrantPerEntryLockContainer] (HotRodServerWorker-1) Creating and acquiring new lock instance for key [B0x0301fe033c000054..[48] 23:50:46,078 TRACE [org.infinispan.util.concurrent.locks.LockManagerImpl] (HotRodServerWorker-1) Successfully acquired lock [B0x0301fe033c000054..[48]!
ISPN config <distributed-cache name="httpSessionCache" mode="ASYNC" start="EAGER" owners="2"> EAP config <cache-container name="web" default-cache="dist" module="org.jboss.as.clustering.web.infinispan"> <transport lock-timeout="60000"/> <replicated-cache name="dist" mode="ASYNC" batching="true"> <remote-store cache="httpSessionCache" socket-timeout="60000" tcp-no-delay="true" shared="true" preload="true" passivation="false" purge="false"> <remote-server outbound-socket-binding="remoteJDGServer"/> </remote-store> </replicated-cache> </cache-container>
This looks to be a bug in EAP. Specifically,
(In reply to Paul Ferraro from comment #3) > This looks to be a bug in EAP. Specifically, https://github.com/jbossas/jboss-eap/pull/2768 https://github.com/jbossas/jboss-eap/pull/2769
Verified with EAP 6.4.9.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.