open-liberty: SessionCache does not work after upgrading to 23.0.0.10
Describe the bug
We are using sessionCache-1.0 (hazelcast) long time now. After upgrading to 23.0.0.10 it is does not work anymore.
Steps to Reproduce
Upgrading from 23.0.0.9 to 23.0.0.10
Expected behavior
The Session will not be synchronized between two Cluster members.
Diagnostic information:
- OpenLiberty Version: 23.0.0.10
- Affected feature(s) sessionCache-1.0
- Java Version: IBM Semeru Runtime Open Edition (17.0.9+9)
- server.xml configuration (WITHOUT sensitive information like passwords)
Our sample server.xml
<variable name="hazelcast.lib" defaultValue="${shared.resource.dir}/hazelcast.jar"/>
<library id="jCacheVendorLib">
<file name="${hazelcast.lib}" />
</library>
<httpSessionCache writeContents="ALL_SESSION_ATTRIBUTES" libraryRef="jCacheVendorLib">
<properties hazelcast.config.location="https://static.server/rest/config/hazelcast-config.xml"/>
</httpSessionCache>
With this hazelcast-config.xml
<hazelcast xmlns="http://www.hazelcast.com/schema/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.hazelcast.com/schema/config
https://hazelcast.com/schema/config/hazelcast-config-5.3.xsd">
<network>
<port auto-increment="false">5708</port>
<join>
<multicast enabled="false"/>
<tcp-ip enabled="true">
<member>vappsae01.domain:5708</member>
<member>vappsae02.domain:5708</member>
</tcp-ip>
</join>
</network>
</hazelcast>
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 44 (20 by maintainers)
Hi @Zech-Hein
I have tried now to delete the LTPAToken2 cookie and then the session replication works fine. The second server has the same values in the session.
Unfortunately the ZIP File from your mail was blocked by IBM policy
Just chiming in here.
This hit us when we bumped from 23.0.0.9 to 23.0.0.10 (presumably because we use LtpaToken and a custom TAI). Downgrading to 23.0.0.9 fixed the issue.
Looking forward to trying out the next version with the fix.
@c-koell thank you for trying that patch, we decided to fix it by reverted the change from https://github.com/OpenLiberty/open-liberty/pull/26704 instead.
@krismarc Yes, it should fix your problem.