Coherence*Web Error Configuring InvocationService "SessionOwnership" For Sticky Session Optimization

(Doc ID 2391239.1)

Last updated on MAY 04, 2018

Applies to:

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

Symptoms

In a 3.7.1.x coherence*web cluster, on start of a weblogic server some applications that use coherence for session persistence says that serializer used by the member 1/managed server-A is different from member 2/managed server-B. When tried to stop other managed servers to see if the server can run alone, but also see the message in that server.





Changes

 

Cause

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