Closed stephan2012 closed 5 years ago
Hazelcast client config for hazelcast-tomcat-sessionmanager:
<?xml version="1.0" encoding="UTF-8"?>
<hazelcast-client xmlns="http://www.hazelcast.com/schema/client-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.hazelcast.com/schema/client-config hazelcast-client-config-3.9.xsd">
<network>
<cluster-members>
<address>hz-tomcat:5701</address>
</cluster-members>
</network>
</hazelcast-client>
@stephan2012 do you want to use the same client for both session or application or different? Also, can you confirm if your application is a Spring or Spring-Boot application & share the Hazelcast Client bean config?
@gokhanoner: Preferably the client is different for session and application management because session replication is handled by ops team while application data is handled by developers. Indeed, it is a Spring application.
Unfortunately I cannot contribute anything anymore to this issue because I have left the team and company in Summer, 2018. In case it does not make sense to continue on this issue please feel free to close it.
@stephan2012 I tried to reproduce your issue, but couldn't manage it. It might be helpful if we have the Hazelcast client version and configuration on application caching side. But you stated you left the team, then I am closing this issue.
At the moment we're running Tomcat 8.5 with built-in session replication. Our webapps include a Hazelcast client for application related caching. This all works without issues.
Now I adjusted the Tomcat config to use Hazelcast as session store and for replication. Unfortunately this seems to conflict with our apps. I already assured that webapp and Tomcat use the same Hazelcast version jars.
This is the Tomcat startup with configured hazelcast-tomcat-sessionmanager:
Deploying the webapp does not succeed anymore with hazelcast-tomcat-sessionmanager:
Looks like there currently is no way of isolating the Hazelcast client for the Tomcat session manager from the app’s client.