Coherence*Web Session Getting Unbound In Spring Application
Last updated on JUNE 22, 2018
Applies to:Oracle Coherence - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Unexpected behavior when integrating a Spring application with Coherence*Web in Weblogic 220.127.116.11.0.
Spring application is configured to store its session information with Coherence*web and defines a Java bean with a clean-up method annotated with the "@PreDestroy" annotation. When accessing Spring controller for the first time (or more generally every time a new session is created), an instance of bean with a session scope is created and stored with the session information. After the Spring controller completes and the response is returned to the client, Coherence seems to be calling a session exit which sends an HTTP Binding Event on the session attributes getting destroyed which is intercepted by Spring (who created the annotated bean and registered itself to listen for session unbind events) and the clean-up method in the bean instance is invoked.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms