Have noticed that one changing the memcache configuration to sticky on my
local setup, the session persists.
Have used the below config. But the concern is
1. The configuration needs to be roundrobin in production
2. This configuration was tested on a single tomcat and single memcache
version on my local setup. So how does it matter whether it is round
robin/sticky configuration when there is only one memcache node
<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
*sticky="true"*
memcachedNodes="n1:localhost:11211"
failoverNodes=""
requestUriIgnorePattern=".*\.(png|gif|jpg|css|js|ico)$"
*sessionBackupAsync="true"*
sessionBackupTimeout="100"
lockingMode="auto"
transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory"
/>
On Monday, 17 September 2018 17:14:41 UTC+10, Deepthi Komatineni wrote:
>
> Hi,
>
> In our project we use AEM 6.3.X version with Tomcat 8.5.31 and memcache
> 1.4.4 version. I observed intermittent session any time after navigating
> from the landing(first) page of the portal.
> There is no session loss when
> 1. Tomcat 8.0.3 version was used
> 2. memcached is not involved i.e. only AEM and tomcat is used
>
> We had to upgrade to tomcat 8.5.31 as 8.0.X has reached end of support.
>
> Is there any known inconsistent or session loss issues on using Tomcat
> 8.5.X version? It seems to work fine with Tomcat 8.0.X version.
>
> Have also tested with Tomcat 8.5.34 and 8.5.0 version. The session is lost
> in these versions too.
>
> Even after upgrading memcached to 1.5.10 from 1.4.4, we notice session
> loss across Tomcat 8.5.X versions.
>
> No errors related to session drop or loss are found in AEM/Tomcat logs.
>
> Can anyone please help?
>
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
