My Oracle Support Banner

Coherence*Web Ignoring Config Parameter "coherence-session-affinity-token" (Doc ID 1475794.1)

Last updated on SEPTEMBER 18, 2023

Applies to:

Oracle Coherence - Version 3.7.1 and later
Information in this document applies to any platform.

Goal

Coherence 3.7.1
 
Coherence*Web ignoring config parameter "coherence-session-affinity".

In order to share sessions between WebLogic and a different application server, in this case Glassfish, there is an issue with the session id: WebLogic appends a character "!" followed by a number (JVM id). In order to recognize this session in another app server (not WebLogic), the session id must omit the part added by WebLogic (!nnnnn).  This is controlled by adding a context param (coherence-session-affinity-token). This is documented here:


     https://docs.oracle.com/cd/E24290_01/coh.371/e22620/cweb_wls.htm#CIHBIFFC
 

The problem is that this parameter is not loaded by Coherence, and the integration does not work.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.