-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
type: bugA general bugA general bug
Description
We are using Spring Session version 1.1.1.RELEASE with Redis and sometimes see the following stacktrace in the log:
2016-04-20 11:07:33,986: ERROR [RedisOperationsSessionRepository] - Error publishing org.springframework.session.events.SessionExpiredEvent[source=org.springframework.session.data.redis.RedisOperationsSessionRepository@3ec0b82f].
java.lang.NullPointerException
at org.springframework.session.web.http.ExpiringSessionHttpSession.getId(ExpiringSessionHttpSession.java:61)
at org.jahia.bin.listeners.JahiaContextLoaderListener.sessionDestroyed(JahiaContextLoaderListener.java:446)
at org.springframework.session.web.http.SessionEventHttpSessionListenerAdapter.onApplicationEvent(SessionEventHttpSessionListenerAdapter.java:62)
at org.springframework.session.web.http.SessionEventHttpSessionListenerAdapter.onApplicationEvent(SessionEventHttpSessionListenerAdapter.java:40)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
at org.springframework.session.data.redis.RedisOperationsSessionRepository.publishEvent(RedisOperationsSessionRepository.java:557)
at org.springframework.session.data.redis.RedisOperationsSessionRepository.handleExpired(RedisOperationsSessionRepository.java:549)
at org.springframework.session.data.redis.RedisOperationsSessionRepository.onMessage(RedisOperationsSessionRepository.java:515)
at org.springframework.data.redis.listener.RedisMessageListenerContainer.executeListener(RedisMessageListenerContainer.java:245)
at org.springframework.data.redis.listener.RedisMessageListenerContainer.processMessage(RedisMessageListenerContainer.java:235)
at org.springframework.data.redis.listener.RedisMessageListenerContainer$1.run(RedisMessageListenerContainer.java:960)
at java.lang.Thread.run(Thread.java:745)
Is this a bug or an expected behaviour? Do we have to expect that NullPointerException or could it be prevented?
yinchuan9527 and sudokai
Metadata
Metadata
Labels
type: bugA general bugA general bug