HttpSessionListener#sessionDestoyed isn't invoked (Tomcat 8)

Description

I have two nodes:

• node 1 -> N1
• node 2 -> N2

Expected behaviour

sessionDestroyed event must be handled by both nodes

Actual behaviour

sessionDestroyed event handled only by N1

Steps to reproduce or test case

WHEN client log in N1 THEN N1 and N2 receive sessionCreated event AND service invalidate session (on N1) THEN sessionDestroyed event handle only N1

Redis version

Redis server v=3.2.6 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=6135068212e7fc88

Redisson version

3.10.7

Redisson configuration

redisson.conf

{
	"singleServerConfig": {
		"idleConnectionTimeout": 10000,
		"pingTimeout": 1000,
		"connectTimeout": 10000,
		"timeout": 3000,
		"retryAttempts": 3,
		"retryInterval": 1500,
		"password": null,
		"subscriptionsPerConnection": 5,
		"clientName": null,
		"address": "redis://some-ip",
		"subscriptionConnectionMinimumIdleSize": 1,
		"subscriptionConnectionPoolSize": 50,
		"connectionMinimumIdleSize": 32,
		"connectionPoolSize": 64,
		"database": 0,
		"dnsMonitoringInterval": 5000
	},
	"threads": 0,
	"nettyThreads": 0,
	"codec": {
		"class": "org.redisson.codec.SerializationCodec"
	},
	"transportMode": "NIO"
}

context.xml

<Manager className="org.redisson.tomcat.RedissonSessionManager"
          configPath="${catalina.base}/conf/redisson.conf" readMode="MEMORY" updateMode="DEFAULT" broadcastSessionEvents="true"/>

[sibmaks]

@mrniko I think that this looks like a bug. Because if I invalidate session on the node then I expect get new a new session. What do you think?

[mrniko]

@JiriFrankCZ

Thanks for checking! Fixed