Bug 1328120

Summary:	[GSS](6.4.z) EAP+JDG sessions entries are removed from cache on shutdown
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Shay Matasaro <smatasar>
Component:	Clustering, Infinispan	Assignee:	Paul Ferraro <paul.ferraro>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	afield, bmaxwell, jbilek, jdg-bugs, jtruhlar, paul.ferraro, rnetuka, wfink
Target Milestone:	CR1
Target Release:	EAP 6.4.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1349047 1370618 (view as bug list)		Environment:
Last Closed:	2017-01-17 12:54:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1324262, 1349047, 1370618

Description Shay Matasaro 2016-04-18 13:57:40 UTC

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]!

Comment 2 Shay Matasaro 2016-04-18 14:05:54 UTC

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>

Comment 3 Paul Ferraro 2016-05-02 15:07:54 UTC

This looks to be a bug in EAP.  Specifically,

Comment 4 Paul Ferraro 2016-05-02 15:08:43 UTC

(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

Comment 6 Jiří Bílek 2016-06-30 14:26:45 UTC

Verified with EAP 6.4.9.CP.CR2

Comment 9 Petr Penicka 2017-01-17 12:54:13 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.